CVE-2024-56749: dlm: fix dlm_recover_members refcount on error
In the Linux kernel, the following vulnerability has been resolved:
dlm: fix dlm_recover_members refcount on error
If dlm_recover_members() fails we don't drop the references of the
previous created root_list that holds and keep all rsbs alive during the
recovery. It might be not an unlikely event because ping_members() could
run into an -EINTR if another recovery progress was triggered again.
Security readout for executives and security teams
Plain-English summary
A Linux kernel error in the Distributed Lock Manager can retain references to cluster-locking objects when membership recovery fails. Repeated recovery interruptions may keep resources alive and degrade availability. The supplied assessment rates this high at CVSS 7.5, but it does not show data theft or modification impact.
Executive priority
Prioritize affected DLM-based clusters because repeated recovery errors may consume resources and disrupt critical clustered services. Treat non-DLM Linux hosts as lower priority after confirming DLM is unused. No supplied evidence supports emergency response for active exploitation, but high-availability environments should remediate promptly.
Technical view
When dlm_recover_members() fails, references held by the previously created root_list are not released, leaving resource blocks alive. The failure can occur when ping_members() returns -EINTR because another recovery begins. This reference leak can accumulate during recovery failures and affect availability.
Likely exposure
Exposure is most relevant to Linux systems actively using DLM for clustered locking and running an affected kernel or vendor backport. The bundle lists 6.10, 6.11.11, 6.12.2, and 6.13 among affected versions, but does not provide a complete distribution-specific package matrix.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public exploit. Although the CVSS vector says network-accessible, the sources do not establish arbitrary Internet exploitation; the defect occurs in DLM membership recovery and primarily threatens availability.
Researcher notes
The defect is a reference-management failure on the dlm_recover_members() error path. The source bundle supplies no CWE, trigger thresholds, memory-growth measurements, crash evidence, or complete vulnerable-version boundaries. Validate exposure against distribution backports rather than kernel version strings alone. Avoid interpreting the network CVSS vector as proof of direct remote reachability.
Mitigation direction
Identify systems using the Linux Distributed Lock Manager and prioritize clustered production workloads.
Check distribution advisories for a kernel package containing the applicable stable fix or backport.
Test and deploy the corrected vendor kernel through normal maintenance procedures.
Reduce repeated cluster recovery conditions where operationally safe until remediation is complete.
Validation and detection
Record running kernel and distribution package versions on systems using DLM.
Confirm the installed package includes the applicable cited stable-kernel commit or vendor backport.
Review cluster logs for repeated recovery restarts, interruptions, or DLM membership failures.
Monitor kernel memory and cluster availability before and after remediation.
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.
cve · low confidence lookup
CVE-2024-56749 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
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.