Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-50015ext4: dax: fix overflowing extents beyond inode size when partially writing

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50015, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 776722e85d3b0936253ecc3d14db4fba37f191ba – < f8a7c342326f6ad1dfdb30a18dd013c70f5e9669
    • affected 776722e85d3b0936253ecc3d14db4fba37f191ba – < 8c30a9a8610c314554997f86370140746aa35661
    • affected 776722e85d3b0936253ecc3d14db4fba37f191ba – < abfaa876b948baaea4d14f21a1963789845c8b4c
    • affected 776722e85d3b0936253ecc3d14db4fba37f191ba – < 5efccdee4a7d507a483f20f880b809cc4eaef14d
    • affected 776722e85d3b0936253ecc3d14db4fba37f191ba – < a9f331f51515bdb3ebc8d0963131af367ef468f6
    • affected 776722e85d3b0936253ecc3d14db4fba37f191ba – < ec0dd451e236c46e4858d53e9e82bae7797a7af5
    • affected 776722e85d3b0936253ecc3d14db4fba37f191ba – < dda898d7ffe85931f9cca6d702a51f33717c501e
  • Linux · Linux

    • affected 4.10
    • unaffected < 4.10
    • unaffected 5.10.227 – ≤ 5.10.*
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.55 – ≤ 6.6.*
    • unaffected 6.10.14 – ≤ 6.10.*
    • unaffected 6.11.3 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50015 badge
[![CVE-2024-50015](https://cveledger.app/badge/CVE-2024-50015.svg)](https://cveledger.app/cve/CVE-2024-50015)

Record last updated .