CVE-2024-35805: dm snapshot: fix lockup in dm_exception_table_exit
In the Linux kernel, the following vulnerability has been resolved:
dm snapshot: fix lockup in dm_exception_table_exit
There was reported lockup when we exit a snapshot with many exceptions.
Fix this by adding "cond_resched" to the loop that frees the exceptions.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35805 is a Linux kernel availability issue in Device Mapper snapshots. When a snapshot with many exceptions is exited, the kernel can lock up while freeing snapshot exception entries. The upstream fix lets the kernel reschedule during that cleanup loop.
Executive priority
Treat this as a targeted availability risk for Linux storage environments, not a broad internet emergency. Prioritize patching where snapshots are operationally important or where device vendors confirm affected firmware.
Technical view
The flaw is in Linux dm snapshot cleanup, specifically dm_exception_table_exit. The reported failure mode is a lockup during snapshot exit with many exceptions. Stable kernel fixes add cond_resched to the exception-freeing loop. No CVSS, CWE, or exploit details are provided in the supplied sources.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions that use dm-snapshot functionality, including snapshot-heavy storage workflows. Debian and Siemens references indicate downstream packaging and product advisory attention, but the bundle does not prove all Linux deployments are reachable or affected in practice.
Exploitation context
The source bundle does not show active exploitation, public exploit code, or CISA KEV listing. The described impact is a lockup condition, so the practical concern is availability rather than data theft or remote code execution based on available evidence.
Researcher notes
Evidence supports a kernel scheduling bug during cleanup of many snapshot exceptions. The bundle lacks root-cause depth beyond the upstream fix description, CVSS scoring, prerequisites, and exploitability analysis. Validate against exact kernel branch fixes and downstream vendor backports.
Mitigation direction
Update affected Linux kernels to vendor-supported fixed builds.
Prioritize systems using Device Mapper or LVM snapshot workflows.
Review Debian LTS and device vendor advisories for packaged fixes.
For appliances, follow Siemens or relevant vendor firmware guidance.
Avoid inventing workarounds; check vendor guidance if patching is delayed.
Validation and detection
Inventory kernel versions against vendor advisories and fixed stable commits.
Identify hosts or appliances using dm-snapshot or LVM snapshots.
Confirm patched kernel packages are installed and active after reboot.
Review monitoring for historical lockups during snapshot cleanup.
Track vendor advisories for affected embedded or managed products.
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-35805 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.