CVE-2026-89494
CVE CVE-2026-89494EUVD EUVD-2026-76400Published 2026-09-11T19:43:45.000ZLast changed 2026-09-14T12:00:28.000ZCVSS 9.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 6714d8e86bf443f6f7af50f9d432025649f091f5 <0e999d56917f861f97adb961617b1828c9eb4733; patch: 6.6.157; 6714d8e86bf443f6f7af50f9d432025649f091f5 <77686fa5bba135252d348e2dacf481fc19f60c41; 6714d8e86bf443f6f7af50f9d432025649f091f5 <50c4cc9183e11f83427efbf770f54851f4471c02; patch: 5.10.270; 6714d8e86bf443f6f7af50f9d432025649f091f5 <a8facb1670b4a0612183198e758d9539ef628ed9; 6714d8e86bf443f6f7af50f9d432025649f091f5 <f33041906885f96e190cde54e61ddc69de39e3ee; patch: 0; patch: 6.1.188; 6714d8e86bf443f6f7af50f9d432025649f091f5 <4a5798253212093b9ff7d90c6cfbe348bcda1594; patch: 7.3-rc1; patch: 5.15.221; 2.6.16; 6714d8e86bf443f6f7af50f9d432025649f091f5 <dce05b17db862f47ff60614017abe639b2e71cad; patch: 7.2.4; patch: 6.18.50; 6714d8e86bf443f6f7af50f9d432025649f091f5 <b54e03d9b3697d25f4a0063cf717d459c5e3ad94; patch: 6.12.109
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.