Answer in brief
CVE-2024-49883 records a Unknown severity vulnerability in ext4: aovid use-after-free in ext4_ext_insert_extent(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-49883 records a Unknown severity vulnerability in ext4: aovid use-after-free in ext4_ext_insert_extent(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=10809df84a4d868db61af621bae3658494165279 <e17ebe4fdd7665c93ae9459ba40fcdfb76769ac1 || >=10809df84a4d868db61af621bae3658494165279 <975ca06f3fd154c5f7742083e7b2574c57d1c0c3 || >=10809df84a4d868db61af621bae3658494165279 <5e811066c5ab709b070659197dccfb80ab650ddd || >=10809df84a4d868db61af621bae3658494165279 <9df59009dfc6d9fc1bd9ddf6c5ab6e56d6ed887a || >=10809df84a4d868db61af621bae3658494165279 <51db04892a993cace63415be99848970a0f15ef2 || >=10809df84a4d868db61af621bae3658494165279 <8162ee5d94b8c0351be0a9321be134872a7654a1 || >=10809df84a4d868db61af621bae3658494165279 <beb7b66fb489041c50c6473100b383f7a51648fc || >=10809df84a4d868db61af621bae3658494165279 <bfed082ce4b1ce6349b05c09a0fa4f3da35ecb1b || >=10809df84a4d868db61af621bae3658494165279 <a164f3a432aae62ca23d03e6d926b122ee5b860d | e17ebe4fdd7665c93ae9459ba40fcdfb76769ac1, 975ca06f3fd154c5f7742083e7b2574c57d1c0c3, 5e811066c5ab709b070659197dccfb80ab650ddd, 9df59009dfc6d9fc1bd9ddf6c5ab6e56d6ed887a, 51db04892a993cace63415be99848970a0f15ef2, 8162ee5d94b8c0351be0a9321be134872a7654a1, beb7b66fb489041c50c6473100b383f7a51648fc, bfed082ce4b1ce6349b05c09a0fa4f3da35ecb1b, a164f3a432aae62ca23d03e6d926b122ee5b860d |
| Linux/Linuxgeneric | 3.18 | Not reported |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we'll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = *ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = *ppath = 2000 if (depth > path[0].p_maxdepth) kfree(path = 2000); *ppath = path = NULL; path = kcalloc() = 3000 *ppath = 3000; return path; /* here path is still 2000, UAF! */ eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: <TASK> ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.
Quoted source text, attributed separately from HOL analysis.
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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=10809df84a4d868db61af621bae3658494165279 <e17ebe4fdd7665c93ae9459ba40fcdfb76769ac1 || >=10809df84a4d868db61af621bae3658494165279 <975ca06f3fd154c5f7742083e7b2574c57d1c0c3 || >=10809df84a4d868db61af621bae3658494165279 <5e811066c5ab709b070659197dccfb80ab650ddd || >=10809df84a4d868db61af621bae3658494165279 <9df59009dfc6d9fc1bd9ddf6c5ab6e56d6ed887a || >=10809df84a4d868db61af621bae3658494165279 <51db04892a993cace63415be99848970a0f15ef2 || >=10809df84a4d868db61af621bae3658494165279 <8162ee5d94b8c0351be0a9321be134872a7654a1 || >=10809df84a4d868db61af621bae3658494165279 <beb7b66fb489041c50c6473100b383f7a51648fc || >=10809df84a4d868db61af621bae3658494165279 <bfed082ce4b1ce6349b05c09a0fa4f3da35ecb1b || >=10809df84a4d868db61af621bae3658494165279 <a164f3a432aae62ca23d03e6d926b122ee5b860d | e17ebe4fdd7665c93ae9459ba40fcdfb76769ac1, 975ca06f3fd154c5f7742083e7b2574c57d1c0c3, 5e811066c5ab709b070659197dccfb80ab650ddd, 9df59009dfc6d9fc1bd9ddf6c5ab6e56d6ed887a, 51db04892a993cace63415be99848970a0f15ef2, 8162ee5d94b8c0351be0a9321be134872a7654a1, beb7b66fb489041c50c6473100b383f7a51648fc, bfed082ce4b1ce6349b05c09a0fa4f3da35ecb1b, a164f3a432aae62ca23d03e6d926b122ee5b860d |
| Linux/Linuxgeneric | 3.18 | Not reported |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ext4: aovid use-after-free in ext4_ext_insert_extent() As Ojaswin mentioned in Link, in ext4_ext_insert_extent(), if the path is reallocated in ext4_ext_create_new_leaf(), we'll use the stale path and cause UAF. Below is a sample trace with dummy values: ext4_ext_insert_extent path = *ppath = 2000 ext4_ext_create_new_leaf(ppath) ext4_find_extent(ppath) path = *ppath = 2000 if (depth > path[0].p_maxdepth) kfree(path = 2000); *ppath = path = NULL; path = kcalloc() = 3000 *ppath = 3000; return path; /* here path is still 2000, UAF! */ eh = path[depth].p_hdr ================================================================== BUG: KASAN: slab-use-after-free in ext4_ext_insert_extent+0x26d4/0x3330 Read of size 8 at addr ffff8881027bf7d0 by task kworker/u36:1/179 CPU: 3 UID: 0 PID: 179 Comm: kworker/u6:1 Not tainted 6.11.0-rc2-dirty #866 Call Trace: <TASK> ext4_ext_insert_extent+0x26d4/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 [...] Allocated by task 179: ext4_find_extent+0x81c/0x1f70 ext4_ext_map_blocks+0x146/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] Freed by task 179: kfree+0xcb/0x240 ext4_find_extent+0x7c0/0x1f70 ext4_ext_insert_extent+0xa26/0x3330 ext4_ext_map_blocks+0xe22/0x2d40 ext4_map_blocks+0x71e/0x1700 ext4_do_writepages+0x1290/0x2800 ext4_writepages+0x26d/0x4e0 do_writepages+0x175/0x700 [...] ================================================================== So use *ppath to update the path to avoid the above problem.
Quoted source text, attributed separately from HOL analysis.