CVE-2026-89494: ocfs2: validate lengths in dlm_mig_lockres_handler
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0e999d56917f861f97adb961617b1828c9eb4733, 4a5798253212093b9ff7d90c6cfbe348bcda1594, 50c4cc9183e11f83427efbf770f54851f4471c02.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0e999d56917f861f97adb961617b1828c9eb4733, 4a5798253212093b9ff7d90c6cfbe348bcda1594, 50c4cc9183e11f83427efbf770f54851f4471c02 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- —
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.16affected
- 6714d8e86bf443f6f7af50f9d432025649f091f5 and later · before 4a5798253212093b9ff7d90c6cfbe348bcda1594affected · git
- 6714d8e86bf443f6f7af50f9d432025649f091f5 and later · before dce05b17db862f47ff60614017abe639b2e71cadaffected · git
- 6714d8e86bf443f6f7af50f9d432025649f091f5 and later · before 0e999d56917f861f97adb961617b1828c9eb4733affected · git
- 6714d8e86bf443f6f7af50f9d432025649f091f5 and later · before 77686fa5bba135252d348e2dacf481fc19f60c41affected · git
- 6714d8e86bf443f6f7af50f9d432025649f091f5 and later · before f33041906885f96e190cde54e61ddc69de39e3eeaffected · git
- 6714d8e86bf443f6f7af50f9d432025649f091f5 and later · before 50c4cc9183e11f83427efbf770f54851f4471c02affected · git
- 6714d8e86bf443f6f7af50f9d432025649f091f5 and later · before a8facb1670b4a0612183198e758d9539ef628ed9affected · git
- 6714d8e86bf443f6f7af50f9d432025649f091f5 and later · before b54e03d9b3697d25f4a0063cf717d459c5e3ad94affected · git
- before 2.6.16not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89492Sep 11, 2026 · ocfs2: validate directory-index entry counts when reading metadata39Monitor
- ← EarlierCVE-2026-89493Sep 11, 2026 · ocfs2: validate rl_used against rl_count in refcount block validator35Monitor
- Later →CVE-2026-89495Sep 11, 2026 · ocfs2: bound namelen in dlm_migrate_request_handler39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0e999d56917f861f97adb961617b1828c9eb4733 | Vendor (CNA) |
| Linux Linux | 4a5798253212093b9ff7d90c6cfbe348bcda1594 | Vendor (CNA) |
| Linux Linux | 50c4cc9183e11f83427efbf770f54851f4471c02 | Vendor (CNA) |
| Linux Linux | 77686fa5bba135252d348e2dacf481fc19f60c41 | Vendor (CNA) |
| Linux Linux | a8facb1670b4a0612183198e758d9539ef628ed9 | Vendor (CNA) |
| Linux Linux | b54e03d9b3697d25f4a0063cf717d459c5e3ad94 | Vendor (CNA) |
| Linux Linux | dce05b17db862f47ff60614017abe639b2e71cad | Vendor (CNA) |
| Linux Linux | f33041906885f96e190cde54e61ddc69de39e3ee | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4a5798253212093b9ff7d90c6cfbe348bcda1594
- git.kernel.org/stable/c/50c4cc9183e11f83427efbf770f54851f4471c02
- git.kernel.org/stable/c/77686fa5bba135252d348e2dacf481fc19f60c41
- git.kernel.org/stable/c/a8facb1670b4a0612183198e758d9539ef628ed9
- git.kernel.org/stable/c/b54e03d9b3697d25f4a0063cf717d459c5e3ad94
- git.kernel.org/stable/c/dce05b17db862f47ff60614017abe639b2e71cad
- git.kernel.org/stable/c/f33041906885f96e190cde54e61ddc69de39e3ee
Vendor advisories and official records. Exploit/PoC links are deliberately left out.