Userspace crashes via dm-flakey zero-page corruption
Published Dec 30, 2025 · Updated Dec 30, 2025
Memory corruption in Linux kernel dm-flakey allows local users to crash userspace programs through writes to a flakey-backed block device. corrupt_bio_data writes an attacker-selected byte into a bio page without excluding the shared ZERO_PAGE(0), breaking the zero-filled-memory guarantee used by mmap and calloc. The path requires a dm-flakey target configured to corrupt writes and a block-zeroing operation; corruption persists system-wide until reboot.
Summary
What happened
Memory corruption in Linux kernel dm-flakey allows local users to crash userspace programs through writes to a flakey-backed block device. corrupt_bio_data writes an attacker-selected byte into a bio page without excluding the shared ZERO_PAGE(0), breaking the zero-filled-memory guarantee used by mmap and calloc. The path requires a dm-flakey target configured to corrupt writes and a block-zeroing operation; corruption persists system-wide until reboot.
The record
- CVE
- CVE-2023-54317
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record 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=1ed7c9f45fb893877ffa7cedd7aa61beaadbb328
- Affected versionversion=5.0
- Affected versionversion=a00f5276e26636cbf72f24f79831026d2e2868e7 <3c4a56ef7c538d16c1738ba0ccea9e7146105b5a
- Affected versionversion=a00f5276e26636cbf72f24f79831026d2e2868e7 <63d31617883d64b43b0e2d529f0751f40713ecae
- Affected versionversion=a00f5276e26636cbf72f24f79831026d2e2868e7 <be360c83f2d810493c04f999d69ec9152981e0c0
- Affected versionversion=a00f5276e26636cbf72f24f79831026d2e2868e7 <f2b478228bfdd11e358c5bc197561331f5d5c394
- Affected versionversion=a00f5276e26636cbf72f24f79831026d2e2868e7 <f50714b57aecb6b3dc81d578e295f86d9c73f078
- Affected versionversion=a00f5276e26636cbf72f24f79831026d2e2868e7 <ff60b2bb680ebcaf8890814dd51084a022891469
- Affected versionversion=c6cd92fcabd6cc78bb1808c6a18245c842722fc1 <b7f8892f672222dbfcc721f51edc03963212b249
- Affected versionversion=d4c637af2e56ee1ec66ee34d0ac5a13c75911aec <98e311be44dbe31ad9c42aa067b2359bac451fda
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