CVE-2026-43125: dlm: validate length in dlm_search_rsb_tree
In the Linux kernel, the following vulnerability has been resolved:
dlm: validate length in dlm_search_rsb_tree
The len parameter in dlm_dump_rsb_name() is not validated and comes
from network messages. When it exceeds DLM_RESNAME_MAXLEN, it can
cause out-of-bounds write in dlm_search_rsb_tree().
Add length validation to prevent potential buffer overflow.
Security readout for executives and security teams
Plain-English summary
CVE-2026-43125 is a Linux kernel DLM flaw where a network-supplied length value is not checked. On affected systems using DLM, this can lead to a kernel buffer overflow with potential full confidentiality, integrity, and availability impact. The sources show fixes and Red Hat advisories, but do not show confirmed active exploitation.
Executive priority
Prioritize remediation for clustered Linux environments and any system where DLM may be reachable over a network. The vulnerability is critical by CVSS and affects kernel code, but urgency should be risk-ranked by confirmed DLM use and vendor package status.
Technical view
The issue is in Linux kernel DLM handling around dlm_dump_rsb_name() and dlm_search_rsb_tree(). A len value from network messages can exceed DLM_RESNAME_MAXLEN, causing an out-of-bounds write. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, score 9.8.
Likely exposure
Exposure is most likely on Linux systems running affected kernels with DLM enabled or used for cluster locking. Systems not using DLM are less likely exposed, but should still validate kernel status because affected-version data in the bundle is broad and distribution-specific.
Exploitation context
The CVSS vector indicates possible network attack surface without credentials or user interaction. However, KEV is false and the provided sources do not cite active exploitation or public exploit availability. Treat this as urgent because kernel memory corruption can have severe outcomes.
Researcher notes
Evidence supports a length-validation bug fixed in Linux stable commits. The source bundle does not provide exploit details, affected distribution matrices beyond Red Hat references, or proof of exploitation. Avoid assuming impact on systems where DLM is absent or unreachable.
Mitigation direction
Apply vendor kernel updates that include the referenced DLM length-validation fix.
Use Red Hat RHSA or your distribution advisory to identify fixed package versions.
Restrict DLM and cluster traffic to trusted cluster nodes only.
Disable DLM where it is not required for the system role.
Reboot into the fixed kernel after patching.
Continue monitoring vendor guidance for distribution-specific status.
Validation and detection
Inventory Linux kernels and map them to vendor CVE advisories.
Check whether DLM is loaded, enabled, or required by cluster services.
Confirm the installed kernel includes a fix or vendor backport for this CVE.
Review firewall rules limiting DLM or cluster traffic to trusted nodes.
Verify patched systems have rebooted into the updated kernel.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-130: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
1ADP providers
19Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-130 · source CWE mapping
Improper Handling of Length Parameter Inconsistency
Improper Handling of Length Parameter Inconsistency represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.