{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89720 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89720 is a high-severity vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89720 and fix it if it is affected.\n\nWhat it is: CVE-2026-89720 is a high-severity vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89720 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89720/ (Markdown: https://insights.sbomify.com/CVE-2026-89720/index.md)","id":"CVE-2026-89720","markdown":"https://insights.sbomify.com/CVE-2026-89720/index.md","name":"CVE-2026-89720","record":{"aliases":["AZL-100085","BELL-CVE-2026-89720","DEBIAN-CVE-2026-89720","GHSA-8388-259p-82vg","UBUNTU-CVE-2026-89720"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel UBIFS","requires_auth":"none","summary":"A crafted UBIFS image triggers an out-of-bounds read in the kernel signature verification, potentially leaking memory contents.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nubifs: fix out-of-bounds read in signature length check\n\nubifs_sb_verify_signature() bounds the on-disk ubifs_sig_node-\u003elen field\nbefore handing the signature payload to verify_pkcs7_signature(), but the\ncheck has the wrong sign:\n\n\tif (le32_to_cpu(signode-\u003elen) \u003e snod-\u003elen + sizeof(struct ubifs_sig_node))\n\nThe signature bytes start sizeof(struct ubifs_sig_node) (UBIFS_SIG_NODE_SZ,\n64 bytes) into the node, so the payload is at most\n\n\tsnod-\u003elen - sizeof(struct ubifs_sig_node)\n\nbytes long. Adding the header size instead of subtracting it accepts a\ndeclared length up to 2 * UBIFS_SIG_NODE_SZ larger than the node actually\nholds -- past the end of c-\u003esbuf, which is vmalloc(c-\u003eleb_size).\nverify_pkcs7_signature() -\u003e pkcs7_parse_message() -\u003e asn1_ber_decoder()\nis then handed that inflated length and reads beyond the allocation while\nwalking the DER headers. The node length comes straight from the mounted\nimage, so a crafted signed UBIFS image reaches this via\nubifs_read_superblock() before the signature is cryptographically checked.\n\nsnod-\u003elen is guaranteed to be \u003e= UBIFS_SIG_NODE_SZ by the node scanner\n(c-\u003eranges[UBIFS_SIG_NODE].min_len == UBIFS_SIG_NODE_SZ), so the corrected\nsubtraction cannot underflow. Legitimately signed images are unaffected: a\ncorrect superblock never declares a signature longer than the node it is\nembedded in.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ubifs: fix out-of-bounds read in signature length check","id":"CVE-2026-89720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"phy: rockchip-samsung-dcphy: fix out-of-range max_register","id":"CVE-2026-89721"},"packages":[],"prev":{"headline":"zram: fix out-of-bounds access in read_block_state()","id":"CVE-2026-89719"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A crafted UBIFS image triggers an out-of-bounds read in the kernel signature verification, potentially leaking memory contents.","url":"https://insights.sbomify.com/CVE-2026-89720/"}