Filesystem corruption via interrupted DAX partial writes
Published Oct 21, 2024 · Updated May 12, 2026
Improper initialization in ext4 DAX in affected Linux kernel branches allows local users to corrupt filesystem metadata by interrupting a write. When dax_iomap_iter stops for a pending fatal signal, dax_iomap_rw reports only copied bytes while leaving later allocated extents marked written beyond the inode size. Exploitation requires write access to a DAX-mounted ext4 filesystem; the resulting extent and inode-size mismatch causes fsck validation to fail.
Summary
What happened
Improper initialization in ext4 DAX in affected Linux kernel branches allows local users to corrupt filesystem metadata by interrupting a write. When dax_iomap_iter stops for a pending fatal signal, dax_iomap_rw reports only copied bytes while leaving later allocated extents marked written beyond the inode size. Exploitation requires write access to a DAX-mounted ext4 filesystem; the resulting extent and inode-size mismatch causes fsck validation to fail.
The record
- CVE
- CVE-2024-50015
- Published
- Oct 21, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
- Classifications
- CWE-665, T1485
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 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 <V3.2
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.
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