Kernel crash via cached released block pointer
Published Jan 19, 2025 · Updated Aug 5, 2026
Double release in the Linux kernel dm-array code allows local users to crash the kernel through corrupted device-mapper cache metadata. When dm_bm_read_lock fails, it releases the faulty block but leaves an invalid pointer that dm_array_cursor caches and releases again in dm_array_cursor_end. Triggering the BUG_ON requires write access to cache metadata on a backing block device and reactivation of the affected cache target.
Summary
What happened
Double release in the Linux kernel dm-array code allows local users to crash the kernel through corrupted device-mapper cache metadata. When dm_bm_read_lock fails, it releases the faulty block but leaves an invalid pointer that dm_array_cursor caches and releases again in dm_array_cursor_end. Triggering the BUG_ON requires write access to cache metadata on a backing block device and reactivation of the affected cache target.
The record
- CVE
- CVE-2024-57929
- Published
- Jan 19, 2025
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-672, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 19, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo