Answer in brief
CVE-2024-50015 records a Unknown severity vulnerability in ext4: dax: fix overflowing extents beyond inode size when partially writing. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=776722e85d3b0936253ecc3d14db4fba37f191ba <f8a7c342326f6ad1dfdb30a18dd013c70f5e9669 || >=776722e85d3b0936253ecc3d14db4fba37f191ba <8c30a9a8610c314554997f86370140746aa35661 || >=776722e85d3b0936253ecc3d14db4fba37f191ba <abfaa876b948baaea4d14f21a1963789845c8b4c || >=776722e85d3b0936253ecc3d14db4fba37f191ba <5efccdee4a7d507a483f20f880b809cc4eaef14d || >=776722e85d3b0936253ecc3d14db4fba37f191ba <a9f331f51515bdb3ebc8d0963131af367ef468f6 || >=776722e85d3b0936253ecc3d14db4fba37f191ba <ec0dd451e236c46e4858d53e9e82bae7797a7af5 || >=776722e85d3b0936253ecc3d14db4fba37f191ba <dda898d7ffe85931f9cca6d702a51f33717c501e | f8a7c342326f6ad1dfdb30a18dd013c70f5e9669, 8c30a9a8610c314554997f86370140746aa35661, abfaa876b948baaea4d14f21a1963789845c8b4c, 5efccdee4a7d507a483f20f880b809cc4eaef14d, a9f331f51515bdb3ebc8d0963131af367ef468f6, ec0dd451e236c46e4858d53e9e82bae7797a7af5, dda898d7ffe85931f9cca6d702a51f33717c501e |
| Linux/Linuxgeneric | 4.10 | Not reported |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.2 | V3.2 |
| Siemens/SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 familygeneric | >=0 <V3.2 | V3.2 |
| Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric | >=0 <V3.2 | V3.2 |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <V1.1.1 | V1.1.1 |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // round 1 ext4_iomap_begin ext4_iomap_alloc // allocate 0~2M extents(written flag) dax_iomap_iter // copy 2M data iomap_iter // round 2 iomap_iter_advance iter->pos += iter->processed // iter->pos = 2M ext4_iomap_begin ext4_iomap_alloc // allocate 2~4M extents(written flag) dax_iomap_iter fatal_signal_pending done = iter->pos - iocb->ki_pos // done = 2M ext4_handle_inode_extension ext4_update_inode_size // inode size = 2M fsck reports: Inode 13, i_size is 2097152, should be 4194304. Fix? Fix the problem by truncating extents if the written length is smaller than expected.
Quoted source text, attributed separately from HOL analysis.