CVE-2024-49983: ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1b558006d98b7b0b730027be0ee98973dd10ee0d, 3ff710662e8d86a63a39b334e9ca0cb10e5c14b0, 5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95; Azure Linux 3.0 ARM 6.6.57.1-2; Azure Linux 3.0 x64 6.6.57.1-2.
Low priority for now. Upgrade to Linux Linux 1b558006d98b7b0b730027be0ee98973dd10ee0d, 3ff710662e8d86a63a39b334e9ca0cb10e5c14b0, 5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95; Azure Linux 3.0 ARM 6.6.57.1-2; Azure Linux 3.0 x64 6.6.57.1-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-415
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10 and later · before 5.10.227
- linux linux kernel5.11 and later · before 5.15.168
- linux linux kernel5.16 and later · before 6.1.113
- linux linux kernel6.2 and later · before 6.6.55
- linux linux kernel6.7 and later · before 6.10.14
- linux linux kernel6.11 and later · before 6.11.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 and later · before 8c26d9e53e5fbacda0732a577e97c5a5b7882aafaffected · git
- 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 and later · before a34bed978364114390162c27e50fca50791c568daffected · git
- 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 and later · before 6367d3f04c69e2b8770b8137bd800e0784b0abbcaffected · git
- 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 and later · before 1b558006d98b7b0b730027be0ee98973dd10ee0daffected · git
- 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 and later · before 3ff710662e8d86a63a39b334e9ca0cb10e5c14b0affected · git
- 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 and later · before 63adc9016917e6970fb0104ee5fd6770f02b2d80affected · git
- 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 and later · before 5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95affected · git
- before 5.10not affected · semver
- 5.10.227 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.115-1 | 6.1.115-1 |
| Debian:13 | linux | before 6.11.4-1 | 6.11.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-49980Oct 21, 2024 · vrf: revert "vrf: Remove unnecessary RCU-bh critical section"22Monitor
- ← EarlierCVE-2024-49981Oct 21, 2024 · media: venus: fix use after free bug in venus_remove due to race condition28Monitor
- Later →CVE-2024-49984Oct 21, 2024 · drm/v3d: Prevent out of bounds access in performance query extensions31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1b558006d98b7b0b730027be0ee98973dd10ee0d | Vendor (CNA) |
| Linux Linux | 3ff710662e8d86a63a39b334e9ca0cb10e5c14b0 | Vendor (CNA) |
| Linux Linux | 5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95 | Vendor (CNA) |
| Linux Linux | 6367d3f04c69e2b8770b8137bd800e0784b0abbc | Vendor (CNA) |
| Linux Linux | 63adc9016917e6970fb0104ee5fd6770f02b2d80 | Vendor (CNA) |
| Linux Linux | 8c26d9e53e5fbacda0732a577e97c5a5b7882aaf | Vendor (CNA) |
| Linux Linux | a34bed978364114390162c27e50fca50791c568d | Vendor (CNA) |
| Azure Linux 3.0 ARM | 6.6.57.1-2 · kernel | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 6.6.57.1-2 · kernel | Microsoft (MSRC) |
| debian:linux | 6.1.115-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-35814157 days apartswiotlb: Fix double-allocation of slots due to broken alignment handling35Monitor
- CVE-2024-498530 days apartfirmware: arm_scmi: Fix double free in OPTEE transport31Monitor
- CVE-2024-498820 days apartext4: fix double brelse() the buffer of the extents path31Monitor
- CVE-2024-499890 days apartdrm/amd/display: fix double free issue during amdgpu module unload31Monitor
- CVE-2024-500550 days apartdriver core: bus: Fix double free in driver API bus_register()31Monitor
- CVE-2024-500717 days apartpinctrl: nuvoton: fix a double free in ma35_pinctrl_dt_node_to_map_func()31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/3ff710662e8d86a63a39b334e9ca0cb10e5c14b0
- git.kernel.org/stable/c/5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95
- git.kernel.org/stable/c/6367d3f04c69e2b8770b8137bd800e0784b0abbc
- git.kernel.org/stable/c/63adc9016917e6970fb0104ee5fd6770f02b2d80
- git.kernel.org/stable/c/8c26d9e53e5fbacda0732a577e97c5a5b7882aaf
- git.kernel.org/stable/c/a34bed978364114390162c27e50fca50791c568d
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.