{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89495 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89495 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-89495 and fix it if it is affected.\n\nWhat it is: CVE-2026-89495 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-89495 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-89495/ (Markdown: https://insights.sbomify.com/CVE-2026-89495/index.md)","id":"CVE-2026-89495","markdown":"https://insights.sbomify.com/CVE-2026-89495/index.md","name":"CVE-2026-89495","record":{"aliases":["AZL-100100","BELL-CVE-2026-89495","DEBIAN-CVE-2026-89495","GHSA-3pmg-pq3r-v8mc","UBUNTU-CVE-2026-89495"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel OCFS2","requires_auth":"none","summary":"A malicious cluster node can trigger heap out-of-bounds writes or panics in the Linux kernel OCFS2 DLM handler via malformed messages.","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: bound namelen in dlm_migrate_request_handler\n\nPatch series \"ocfs2/dlm: bound peer-controlled lengths in the o2dlm\".\n\nThe o2dlm receive handlers trust u8 length and count fields from the wire\nwithout bounding them, so a node in a DLM domain can corrupt or panic any\nother node with a malformed message.  Three defects:\n\n  - dlm_migrate_request_handler() passes migrate-\u003enamelen unchecked to\n    dlm_init_mle(), which memcpy()s it into the 32-byte mname[] of an\n    o2dlm_mle slab object: a heap out-of-bounds write of up to ~215\n    attacker-controlled bytes.\n\n  - dlm_mig_lockres_handler() passes mres-\u003elockname_len unchecked to\n    dlm_init_lockres(), which memcpy()s it into the 32-byte o2dlm_lockname\n    slab object: a heap out-of-bounds write of up to ~223 bytes.\n\n  - the same handler trusts mres-\u003enum_locks without checking that the\n    message is large enough to hold that many entries, so\n    dlm_process_recovery_data() walks mres-\u003eml[] past the kmalloc(data_len)\n    copy and trips a BUG_ON (an out-of-bounds read ending in a panic).\n\nThe other o2dlm receive handlers already reject an oversized name; the\nmigration and recovery handlers have omitted it since the DLM was added\n(see the Fixes tags).  Patch 1 bounds namelen; patch 2 validates\nlockname_len, num_locks, and the payload size.  Conforming recovery and\nmigration traffic is unaffected.\n\no2net authenticates peers only by the DLM domain key, so any node that has\njoined the domain -- including a compromised or malicious member -- can\nsend these messages.  There is no local trigger; the attacker must already\nbe a member of the cluster.\n\nEach sink was confirmed under KASAN with an out-of-tree module mirroring\nit exactly -- a kmem_cache/kmalloc of the real destination size, then the\nsame unclamped memcpy/loop: slab-out-of-bounds Write for the two writes,\nRead for the recovery walk, and a panic.  A userspace AddressSanitizer\nbuild faults identically under -m32 and -m64.  Scrubbed logs are available\non request.\n\nI reported this privately to security@kernel.org and the ocfs2 maintainers\non 2026-06-20; with no response after the standard embargo period I am\nposting the fix publicly.  I have no embargo requirement.\n\nThis patch (of 2):\n\nA node receiving a DLM_MIGRATE_REQUEST message trusts the peer-supplied\nname length (migrate-\u003enamelen) without bounding it.  dlm_init_mle() then\ncopies that many bytes into the fixed DLM_LOCKID_NAME_MAX-byte mname[]\narray of an o2dlm_mle slab object, so a malformed message from a cluster\npeer overflows the slab object by up to ~215 bytes: a heap out-of-bounds\nwrite of attacker-controlled data, reachable by any node in the domain.\n\nReject an oversized name, the way dlm_master_request_handler() and the\nother o2dlm receive handlers already do; the migration handler omits the\ncheck entirely.  Conforming 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: bound namelen in dlm_migrate_request_handler","id":"CVE-2026-89495","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: always run deallocs on copy-on-write completion","id":"CVE-2026-89496"},"packages":[],"prev":{"headline":"ocfs2: validate lengths in dlm_mig_lockres_handler","id":"CVE-2026-89494"},"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 malicious cluster node can trigger heap out-of-bounds writes or panics in the Linux kernel OCFS2 DLM handler via malformed messages.","url":"https://insights.sbomify.com/CVE-2026-89495/"}