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-49881ext4: update orig_path in ext4_find_extent()

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don't update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = *ppath = 2000 ext4_find_extent if (depth > path[0].p_maxdepth) kfree(path = 2000); *orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(*ppath = NULL) path = *ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: <TASK> ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.

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-49881, 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.25% · top 83% of all CVEs (20 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 10809df84a4d868db61af621bae3658494165279 – < ec0c0beb9b777cdd1edd7df9b36e0f3e67e2bdff
    • affected 10809df84a4d868db61af621bae3658494165279 – < 6766937d0327000ac1b87c97bbecdd28b0dd6599
    • affected 10809df84a4d868db61af621bae3658494165279 – < a9fcb1717d75061d3653ed69365c8d45331815cd
    • affected 10809df84a4d868db61af621bae3658494165279 – < 6801ed1298204d16a38571091e31178bfdc3c679
    • affected 10809df84a4d868db61af621bae3658494165279 – < f55ecc58d07a6c1f6d6d5b5af125c25f8da0bda2
    • affected 10809df84a4d868db61af621bae3658494165279 – < b63481b3a388ee2df9e295f97273226140422a42
    • affected 10809df84a4d868db61af621bae3658494165279 – < 11b230100d6801c014fab2afabc8bdea304c1b96
    • affected 10809df84a4d868db61af621bae3658494165279 – < 5b4b2dcace35f618fe361a87bae6f0d13af31bc1
  • Linux · Linux

    • affected 3.18
    • unaffected < 3.18
    • unaffected 4.19.323 – ≤ 4.19.*
    • 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

References12

Sources

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

Badge for a README or a ticket

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

Record last updated .