CVE-2024-49983: Linux kernel · ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.8 High · fixed in 5.15.0-1073.79~20.04.1 : patch Linux kernel soon.
Data as of 29 Oct 2026, 22:34 UTC
- Patch
- Available – fixed in 5.15.0-1073.79~20.04.1, 5.15.0-1078.87~20.04.1, 5.15.0-1072.80~20.04.1 +58
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7166-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7194-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7304-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2024-49983 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-49983 (opens in a new tab)
- git.kernel.org/linus/5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95 (opens in a new tab)
- git.kernel.org/stable/c/8c26d9e53e5fbacda0732a577e97c5a5b7882aaf (opens in a new tab)
- git.kernel.org/stable/c/a34bed978364114390162c27e50fca50791c568d (opens in a new tab)
- git.kernel.org/stable/c/6367d3f04c69e2b8770b8137bd800e0784b0abbc (opens in a new tab)
- git.kernel.org/stable/c/1b558006d98b7b0b730027be0ee98973dd10ee0d (opens in a new tab)
- git.kernel.org/stable/c/3ff710662e8d86a63a39b334e9ca0cb10e5c14b0 (opens in a new tab)
- git.kernel.org/stable/c/63adc9016917e6970fb0104ee5fd6770f02b2d80 (opens in a new tab)
- git.kernel.org/stable/c/5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7194-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)