{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89494 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89494 is a critical memory corruption vulnerability in Linux, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89494 and fix it if it is affected.\n\nWhat it is: CVE-2026-89494 is a critical memory corruption vulnerability in Linux, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89494 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-89494/ (Markdown: https://insights.sbomify.com/CVE-2026-89494/index.md)","id":"CVE-2026-89494","markdown":"https://insights.sbomify.com/CVE-2026-89494/index.md","name":"CVE-2026-89494","record":{"aliases":["AZL-100680","BELL-CVE-2026-89494","DEBIAN-CVE-2026-89494","GHSA-hhc4-rpwx-gp2p","UBUNTU-CVE-2026-89494"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel OCFS2","requires_auth":"none","summary":"A remote attacker can trigger out-of-bounds reads and writes in the Linux kernel OCFS2 DLM handler, causing a system crash or potential code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: validate lengths in dlm_mig_lockres_handler\n\nA node receiving a DLM_MIG_LOCKRES message trusts several fields of the\npeer-supplied dlm_migratable_lockres without validation.  num_locks and\nlockname_len are bounded only on the sending side, and the message is\nnever checked to actually carry num_locks migratable_lock entries.  As a\nresult dlm_process_recovery_data() walks mres-\u003eml[0..num_locks) past the\nkmalloc(data_len) copy of the message (an out-of-bounds read that ends in\na BUG_ON panic), and dlm_init_lockres() copies lockname_len bytes into the\nfixed 32-byte o2dlm_lockname slab object (a heap out-of-bounds write). \nBoth are reachable by any node in the domain.\n\nValidate these fields right after dlm_grab(), before anything uses them --\nincluding the not-joined error path, which already prints mres-\u003elockname\nwith the unbounded lockname_len as a %.*s precision.  Reject the message\nunless lockname_len \u003c= DLM_LOCKID_NAME_MAX, num_locks \u003c=\nDLM_MAX_MIGRATABLE_LOCKS (the bound the sender already asserts), and the\npayload is large enough to hold the claimed locks.  Conforming recovery\nand migration messages are unaffected.","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":"ocfs2: validate lengths in dlm_mig_lockres_handler","id":"CVE-2026-89494","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ocfs2: bound namelen in dlm_migrate_request_handler","id":"CVE-2026-89495"},"packages":[],"prev":{"headline":"ocfs2: validate rl_used against rl_count in refcount block validator","id":"CVE-2026-89493"},"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 remote attacker can trigger out-of-bounds reads and writes in the Linux kernel OCFS2 DLM handler, causing a system crash or potential code execution.","url":"https://insights.sbomify.com/CVE-2026-89494/"}