CVE-2024-49960: ext4: fix timer use-after-free on failed mount
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.28% (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 0ce160c5bdb67081a62293028dc85758a8efb22a, 22e9b83f0f33bc5a7a3181769d1dccbf021f5b04, 5.10.237; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2.
Low priority for now. Upgrade to Linux Linux 0ce160c5bdb67081a62293028dc85758a8efb22a, 22e9b83f0f33bc5a7a3181769d1dccbf021f5b04, 5.10.237; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 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: fix timer use-after-free on failed mount Syzbot has found an ODEBUG bug in ext4_fill_super The del_timer_sync function cancels the s_err_report timer, which reminds about filesystem errors daily. We should guarantee the timer is no longer active before kfree(sbi). When filesystem mounting fails, the flow goes to failed_mount3, where an error occurs when ext4_stop_mmpd is called, causing a read I/O failure. This triggers the ext4_handle_error function that ultimately re-arms the timer, leaving the s_err_report timer active before kfree(sbi) is called. Fix the issue by canceling the s_err_report timer after calling ext4_stop_mmpd.
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-416
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
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernelbefore 5.10.237
- linux linux kernel5.11 and later · before 5.15.181
- linux linux kernel5.16 and later · before 6.1.118
- 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
- cecfdb9cf9a700d1037066173abac0617f6788df, eb7b40d9d3785f7a131fb0b1f89bb6efa46c1833, 5.14affected
- 5e4f5138bd8522ebe231a137682d3857209a2c07 and later · before 7aac0c17a8cdf4a3236991c1e60435c6a984076caffected · git
- 618f003199c6188e01472b03cdbba227f1dc5f24 and later · before 22e9b83f0f33bc5a7a3181769d1dccbf021f5b04affected · git
- 618f003199c6188e01472b03cdbba227f1dc5f24 and later · before cf3196e5e2f36cd80dab91ffae402e13935724bcaffected · git
- 618f003199c6188e01472b03cdbba227f1dc5f24 and later · before 9203817ba46ebba7c865c8de2aba399537b6e891affected · git
- 618f003199c6188e01472b03cdbba227f1dc5f24 and later · before fa78fb51d396f4f2f80f8e96a3b1516f394258beaffected · git
- 618f003199c6188e01472b03cdbba227f1dc5f24 and later · before b85569585d0154d4db1e4f9e3e6a4731d407feb0affected · git
- 618f003199c6188e01472b03cdbba227f1dc5f24 and later · before 0ce160c5bdb67081a62293028dc85758a8efb22aaffected · git
- 5.10.51 and later · before 5.10.237affected · semver
- 5.12.18 and later · before 5.13affected · 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.119-1 | 6.1.119-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-49958Oct 21, 2024 · ocfs2: reserve space for inline xattr before attaching reflink tree22Monitor
- ← EarlierCVE-2024-49959Oct 21, 2024 · jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error22Monitor
- Later →CVE-2024-49961Oct 21, 2024 · media: i2c: ar0521: Use cansleep version of gpiod_set_value()22Monitor
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 | 0ce160c5bdb67081a62293028dc85758a8efb22a | Vendor (CNA) |
| Linux Linux | 22e9b83f0f33bc5a7a3181769d1dccbf021f5b04 | Vendor (CNA) |
| Linux Linux | 5.10.237 | Vendor (CNA) |
| Linux Linux | 5.13 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 7aac0c17a8cdf4a3236991c1e60435c6a984076c | Vendor (CNA) |
| Linux Linux | 9203817ba46ebba7c865c8de2aba399537b6e891 | Vendor (CNA) |
| Linux Linux | b85569585d0154d4db1e4f9e3e6a4731d407feb0 | Vendor (CNA) |
| Linux Linux | cf3196e5e2f36cd80dab91ffae402e13935724bc | Vendor (CNA) |
| Linux Linux | fa78fb51d396f4f2f80f8e96a3b1516f394258be | Vendor (CNA) |
| azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 | 6.6.57.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 | 6.6.57.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0 | CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.180.1-1 on CBL-Mariner 2.0 | 5.15.182.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.119-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.
No nightly-computed relations.
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-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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/22e9b83f0f33bc5a7a3181769d1dccbf021f5b04
- git.kernel.org/stable/c/7aac0c17a8cdf4a3236991c1e60435c6a984076c
- git.kernel.org/stable/c/9203817ba46ebba7c865c8de2aba399537b6e891
- git.kernel.org/stable/c/b85569585d0154d4db1e4f9e3e6a4731d407feb0
- git.kernel.org/stable/c/cf3196e5e2f36cd80dab91ffae402e13935724bc
- git.kernel.org/stable/c/fa78fb51d396f4f2f80f8e96a3b1516f394258be
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.