Answer in brief
CVE-2024-49983 records a Unknown severity vulnerability in ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free. 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-49983 records a Unknown severity vulnerability in ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free. 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 | >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <8c26d9e53e5fbacda0732a577e97c5a5b7882aaf || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <a34bed978364114390162c27e50fca50791c568d || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <6367d3f04c69e2b8770b8137bd800e0784b0abbc || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <1b558006d98b7b0b730027be0ee98973dd10ee0d || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <3ff710662e8d86a63a39b334e9ca0cb10e5c14b0 || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <63adc9016917e6970fb0104ee5fd6770f02b2d80 || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95 | 8c26d9e53e5fbacda0732a577e97c5a5b7882aaf, a34bed978364114390162c27e50fca50791c568d, 6367d3f04c69e2b8770b8137bd800e0784b0abbc, 1b558006d98b7b0b730027be0ee98973dd10ee0d, 3ff710662e8d86a63a39b334e9ca0cb10e5c14b0, 63adc9016917e6970fb0104ee5fd6770f02b2d80, 5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95 |
| Linux/Linuxgeneric | 5.10 | 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: drop ppath from ext4_ext_replay_update_ex() to avoid double-free When calling ext4_force_split_extent_at() in ext4_ext_replay_update_ex(), the 'ppath' is updated but it is the 'path' that is freed, thus potentially triggering a double-free in the following process: ext4_ext_replay_update_ex ppath = path ext4_force_split_extent_at(&ppath) ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth ext4_find_extent if (depth > path[0].p_maxdepth) kfree(path) ---> path First freed *orig_path = path = NULL ---> null ppath kfree(path) ---> path double-free !!! So drop the unnecessary ppath and use path directly to avoid this problem. And use ext4_find_extent() directly to update path, avoiding unnecessary memory allocation and freeing. Also, propagate the error returned by ext4_find_extent() instead of using strange error codes.
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 | >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <8c26d9e53e5fbacda0732a577e97c5a5b7882aaf || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <a34bed978364114390162c27e50fca50791c568d || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <6367d3f04c69e2b8770b8137bd800e0784b0abbc || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <1b558006d98b7b0b730027be0ee98973dd10ee0d || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <3ff710662e8d86a63a39b334e9ca0cb10e5c14b0 || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <63adc9016917e6970fb0104ee5fd6770f02b2d80 || >=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95 | 8c26d9e53e5fbacda0732a577e97c5a5b7882aaf, a34bed978364114390162c27e50fca50791c568d, 6367d3f04c69e2b8770b8137bd800e0784b0abbc, 1b558006d98b7b0b730027be0ee98973dd10ee0d, 3ff710662e8d86a63a39b334e9ca0cb10e5c14b0, 63adc9016917e6970fb0104ee5fd6770f02b2d80, 5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95 |
| Linux/Linuxgeneric | 5.10 | 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: drop ppath from ext4_ext_replay_update_ex() to avoid double-free When calling ext4_force_split_extent_at() in ext4_ext_replay_update_ex(), the 'ppath' is updated but it is the 'path' that is freed, thus potentially triggering a double-free in the following process: ext4_ext_replay_update_ex ppath = path ext4_force_split_extent_at(&ppath) ext4_split_extent_at ext4_ext_insert_extent ext4_ext_create_new_leaf ext4_ext_grow_indepth ext4_find_extent if (depth > path[0].p_maxdepth) kfree(path) ---> path First freed *orig_path = path = NULL ---> null ppath kfree(path) ---> path double-free !!! So drop the unnecessary ppath and use path directly to avoid this problem. And use ext4_find_extent() directly to update path, avoiding unnecessary memory allocation and freeing. Also, propagate the error returned by ext4_find_extent() instead of using strange error codes.
Quoted source text, attributed separately from HOL analysis.