CVE-2026-89494Critical· 9.8▾ MidnightIn the Linux kernel, the following vulnerability has been resolved: ocfs2: validate lengths in dlm_mig_lockres_handler A node receiving a DLM_MIG_LOCKRES message trusts several fields of the peer-supplied dlm_migratable_lockres without…
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
— → 6.6
none → medium
— → 9.8
none → critical
9.8 → 6.6
critical → medium
6.6 → 9.8
medium → critical
0.2% → 0.8%
9.8 → 5.5
critical → medium
Last analysed / modified upstream
5.5 → 9.8
medium → critical
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: validate lengths in dlm_mig_lockres_handler
A node receiving a DLM_MIG_LOCKRES message trusts several fields of the peer-supplied dlm_migratable_lockres without validation. num_locks and lockname_len are bounded only on the sending side, and the message is never checked to actually carry num_locks migratable_lock entries. As a result dlm_process_recovery_data() walks mres->ml[0..num_locks) past the kmalloc(data_len) copy of the message (an out-of-bounds read that ends in a BUG_ON panic), and dlm_init_lockres() copies lockname_len bytes into the fixed 32-byte o2dlm_lockname slab object (a heap out-of-bounds write). Both are reachable by any node in the domain.
Validate these fields right after dlm_grab(), before anything uses them -- including the not-joined error path, which already prints mres->lockname with the unbounded lockname_len as a %.*s precision. Reject the message unless lockname_len <= DLM_LOCKID_NAME_MAX, num_locks <= DLM_MAX_MIGRATABLE_LOCKS (the bound the sender already asserts), and the payload is large enough to hold the claimed locks. Conforming recovery and migration messages are unaffected.
Linux >= 6714d8e86bf443f6f7af50f9d432025649f091f5 < 4a5798253212093b9ff7d90c6cfbe348bcda1594Linux >= 6714d8e86bf443f6f7af50f9d432025649f091f5 < dce05b17db862f47ff60614017abe639b2e71cadLinux >= 6714d8e86bf443f6f7af50f9d432025649f091f5 < 0e999d56917f861f97adb961617b1828c9eb4733Linux >= 6714d8e86bf443f6f7af50f9d432025649f091f5 < 77686fa5bba135252d348e2dacf481fc19f60c41Linux >= 6714d8e86bf443f6f7af50f9d432025649f091f5 < f33041906885f96e190cde54e61ddc69de39e3eeLinux >= 6714d8e86bf443f6f7af50f9d432025649f091f5 < 50c4cc9183e11f83427efbf770f54851f4471c02Linux >= 6714d8e86bf443f6f7af50f9d432025649f091f5 < a8facb1670b4a0612183198e758d9539ef628ed9Linux >= 6714d8e86bf443f6f7af50f9d432025649f091f5 < b54e03d9b3697d25f4a0063cf717d459c5e3ad94Linux 2.6.16Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-57804High· 7.3scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs
CVE-2024-47794High· 7.8bpf: Prevent tailcall infinite loop caused by freplace
CVE-2025-39977High· 7.8In the Linux kernel, the following vulnerability has been resolved: futex: Prevent use-after-free during requeue-PI syzbot managed to trigger the following race: T1 T2 futex_wait_requeue_pi() fute…
CVE-2026-100070Medium· 5.5In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_nat_sip: rewind offset when NAT shrinks the packet sashiko says: If map_addr() changes the packet length, such as when the public NAT IP string is shor…
CVE-2026-100071Medium· 5.5In the Linux kernel, the following vulnerability has been resolved: net: hsr: free learned nodes on device setup failure hsr_dev_finalize() can fail after a lower-device RX handler has already been registered (slave A is added before t…
CVE-2024-38564High· 7.8bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE