CVE-2026-53043 — Linux kernel ocfs2 DLM - missing bounds check in dlm_match_regions()
In the Linux kernel, the following vulnerability has been resolved: ocfs2/dlm: validate qr_numregions in dlm_match_regions() Patch series "ocfs2/dlm: fix two bugs in dlm_match_regions()". In dlm_match_regions(), the qr_numregions field from a DLM_QUERY_REGION network message is used to drive loops over the qr_regions buffer without sufficient validation. This series fixes two issues: - Patch 1 adds a bounds check to reject messages where qr_numregions exceeds O2NM_MAX_REGIONS. The o2net layer only validates message byte length; it does not constrain field values, so a crafted message can set qr_numregions up to 255 and trigger out-of-bounds reads past the 1024-byte qr_regions buffer. - Patch 2 fixes an off-by-one in the local-vs-remote comparison loop, which uses '<=' instead of '<', reading one entry past the valid range even when qr_numregions is within bounds. This patch (of 2): The qr_numregions field from a DLM_QUERY_REGION network message is used directly as loop bounds in dlm_match_regions() without checking against O2NM_MAX_REGIONS. Since qr_regions is sized for at most O2NM_MAX_REGIONS (32) entries, a crafted message with qr_numregions > 32 causes out-of-bounds reads past the qr_regions buffer. Add a bounds check for qr_numregions before entering the loops.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.5% (30-day exploitation probability)+6
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ ea2034416b54700e30371f2ad6517cbb94674083 and < d3d5efade0c79dac1cac98c0cb1115432f804439≥ ea2034416b54700e30371f2ad6517cbb94674083 and < f69551139caf6d24242a0ad049ee46b264e3aee0≥ ea2034416b54700e30371f2ad6517cbb94674083 and < 1f8b91275912cd428289c1fb424bebd7ff5302bd≥ ea2034416b54700e30371f2ad6517cbb94674083 and < f37de46149db49abd2b24f4f0c5a88cf4dfb5f47≥ ea2034416b54700e30371f2ad6517cbb94674083 and < 6c6e8fc3c007319981647b410c29bb5775048551≥ ea2034416b54700e30371f2ad6517cbb94674083 and < 3f474c33ebc2e2ca3fcb587d7de4375348f13373≥ ea2034416b54700e30371f2ad6517cbb94674083 and < 3c2d0de23ae4be22b6c18e8f0915be74d3b5fb21≥ ea2034416b54700e30371f2ad6517cbb94674083 and < 7ab3fbb01bc6d79091bc375e5235d360cd9b78be and 1 moreversion 2.6.37 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 2.6.37 and < 5.10.258≥ 5.11 and < 5.15.209≥ 5.16 and < 6.1.175≥ 6.2 and < 6.6.141≥ 6.7 and < 6.12.91≥ 6.13 and < 6.18.33≥ 6.19 and < 7.0.10 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.1 | CVSS 3.1 | Critical | 3.9 | 5.2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 9.1 | CVSS 3.1 | Critical | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.74%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Analysis and videos
CVE-2026-53043: Linux kernel ocfs2 DLM - missing bounds check in dlm_match_regions()
The Linux kernel ocfs2 distributed lock manager uses the qr_numregions field of incoming DLM_QUERY_REGION messages as loop bounds without checking it first. According to the record, a crafted message can cause out-of-bounds memory access, and the CNA rates it Critical with CVSS 3.1 score 9.1. The record lists stable kernel fix commits, and no confirmed exploitation appears in the sources consulted.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 9.1
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/f69551139caf6d24242a0ad049ee46b264e3aee0
- git.kernel.org/stable/c/6c6e8fc3c007319981647b410c29bb5775048551
- git.kernel.org/stable/c/3f474c33ebc2e2ca3fcb587d7de4375348f13373
- git.kernel.org/stable/c/1f8b91275912cd428289c1fb424bebd7ff5302bd
- git.kernel.org/stable/c/f37de46149db49abd2b24f4f0c5a88cf4dfb5f47
- git.kernel.org/stable/c/3c2d0de23ae4be22b6c18e8f0915be74d3b5fb21
- git.kernel.org/stable/c/d3d5efade0c79dac1cac98c0cb1115432f804439
- git.kernel.org/stable/c/7ab3fbb01bc6d79091bc375e5235d360cd9b78be
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 17h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 17h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-53043 is "Linux kernel ocfs2 DLM - missing bounds check in dlm_match_regions()", rated Critical. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.1 describes technical severity. EPSS 0.51% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.