CVE-2024-35859: block: fix module reference leakage from bdev_open_by_dev error path
In the Linux kernel, the following vulnerability has been resolved:
block: fix module reference leakage from bdev_open_by_dev error path
At the time bdev_may_open() is called, module reference is grabbed
already, hence module reference should be released if bdev_may_open()
failed.
This problem is found by code review.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35859 is a Linux kernel availability issue in block-device handling. A failed device-open permission check can leak a module reference, potentially leaving resources stuck and affecting system availability. It requires local access with privileges and has no cited evidence of active exploitation.
Executive priority
Treat as routine but real patching work. The business risk is service disruption on affected Linux hosts, not data theft. Prioritize multi-user, internet-facing, and high-availability infrastructure in normal kernel maintenance windows.
Technical view
The flaw is in the Linux kernel block layer error path for bdev_open_by_dev. bdev_may_open is called after a module reference is already acquired, but failure did not release that reference. The issue was found by code review and fixed in referenced stable commits.
Likely exposure
Exposure is mainly Linux systems running affected kernel builds listed in the source bundle, including 6.8-era entries. Distro kernels may differ because of backports, so confirm by vendor advisory or kernel changelog.
Exploitation context
The CVSS vector is local, low complexity, low privilege, no user interaction, with high availability impact and no confidentiality or integrity impact. KEV is false, and the source bundle provides no evidence of public exploitation.
Researcher notes
The source identifies a module reference leak in an error path, not a memory corruption issue. Affected-version evidence is limited in the bundle; validate exact exposure against vendor kernel sources and stable commit inclusion.
Mitigation direction
Update to a vendor kernel containing the referenced Linux stable fixes.
Check distribution advisories for backported package versions.
Prioritize shared servers and systems with untrusted local users.
If no update is available, follow vendor guidance; no workaround is cited.
Validation and detection
Inventory Linux kernel versions across affected hosts.
Check kernel package changelogs for the referenced stable commits.
Confirm scanners map distro backports, not only upstream version strings.
Review local-user exposure on systems awaiting patches.
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-35859 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.