Kernel crash via unsynchronized bitmap statistics read
Published Feb 27, 2025 · Updated Aug 5, 2026
A use-after-free in Linux kernel md bitmap statistics allows local users to crash the kernel by reading md array status. bitmap_get_stats() dereferences bitmap and bitmap->storage without synchronizing with bitmap_info.mutex when the bitmap is destroyed or incompletely initialized. The path is reachable while an md device remains present, and successful triggering causes a kernel panic rather than data access or code execution.
Summary
What happened
A use-after-free in Linux kernel md bitmap statistics allows local users to crash the kernel by reading md array status. bitmap_get_stats() dereferences bitmap and bitmap->storage without synchronizing with bitmap_info.mutex when the bitmap is destroyed or incompletely initialized. The path is reachable while an md device remains present, and successful triggering causes a kernel panic rather than data access or code execution.
The record
- CVE
- CVE-2025-21712
- Published
- Feb 27, 2025
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-20, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 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=V3.1.5 <*
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