CVE-2024-40998: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super()
Noroxi assessment
Priority: Monitor (action score 22/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.27% (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 1e2df0ee0afd6d4b436a740f04f7a759e6531005, 23afcd52af06880c6c913a0ad99022b8937b575c, 645267906944a9aeec9d5c56ee24a9096a288798.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1e2df0ee0afd6d4b436a740f04f7a759e6531005, 23afcd52af06880c6c913a0ad99022b8937b575c, 645267906944a9aeec9d5c56ee24a9096a288798 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 uninitialized ratelimit_state->lock access in __ext4_fill_super() In the following concurrency we will access the uninitialized rs->lock: ext4_fill_super ext4_register_sysfs // sysfs registered msg_ratelimit_interval_ms // Other processes modify rs->interval to // non-zero via msg_ratelimit_interval_ms ext4_orphan_cleanup ext4_msg(sb, KERN_INFO, "Errors on filesystem, " __ext4_msg ___ratelimit(&(EXT4_SB(sb)->s_msg_ratelimit_state) if (!rs->interval) // do nothing if interval is 0 return 1; raw_spin_trylock_irqsave(&rs->lock, flags) raw_spin_trylock(lock) _raw_spin_trylock __raw_spin_trylock spin_acquire(&lock->dep_map, 0, 1, _RET_IP_) lock_acquire __lock_acquire register_lock_class assign_lock_key dump_stack(); ratelimit_state_init(&sbi->s_msg_ratelimit_state, 5 * HZ, 10); raw_spin_lock_init(&rs->lock); // init rs->lock here and get the following dump_stack: ========================================================= INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this object before use? turning off the locking correctness validator. CPU: 12 PID: 753 Comm: mount Tainted: G E 6.7.0-rc6-next-20231222 #504 [...] Call Trace: dump_stack_lvl+0xc5/0x170 dump_stack+0x18/0x30 register_lock_class+0x740/0x7c0 __lock_acquire+0x69/0x13a0 lock_acquire+0x120/0x450 _raw_spin_trylock+0x98/0xd0 ___ratelimit+0xf6/0x220 __ext4_msg+0x7f/0x160 [ext4] ext4_orphan_cleanup+0x665/0x740 [ext4] __ext4_fill_super+0x21ea/0x2b10 [ext4] ext4_fill_super+0x14d/0x360 [ext4] [...] ========================================================= Normally interval is 0 until s_msg_ratelimit_state is initialized, so ___ratelimit() does nothing. But registering sysfs precedes initializing rs->lock, so it is possible to change rs->interval to a non-zero value via the msg_ratelimit_interval_ms interface of sysfs while rs->lock is uninitialized, and then a call to ext4_msg triggers the problem by accessing an uninitialized rs->lock. Therefore register sysfs after all initializations are complete to avoid such problems.
- Published
- Jul 12, 2024
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- CWE-908
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 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.
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 kernelbefore 6.6.36
- linux linux kernel6.7 and later · before 6.9.7
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
- 3.13affected
- efbed4dc5857f845d787e406ce85097d1ccc5c4f and later · before 1e2df0ee0afd6d4b436a740f04f7a759e6531005affected · git
- efbed4dc5857f845d787e406ce85097d1ccc5c4f and later · before 23afcd52af06880c6c913a0ad99022b8937b575caffected · git
- efbed4dc5857f845d787e406ce85097d1ccc5c4f and later · before 645267906944a9aeec9d5c56ee24a9096a288798affected · git
- efbed4dc5857f845d787e406ce85097d1ccc5c4f and later · before b4b4fda34e535756f9e774fb2d09c4537b7dfd1caffected · git
- before 3.13not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.36 and later · up to and including 6.6.*not affected · semver
- 6.9.7 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.3.0-427.42.1.el9_4 | 7.3.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.42.1.el9_4 | 5.14.0-427.42.1.el9_4 |
+96
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-40993Jul 12, 2024 · netfilter: ipset: Fix suspicious rcu_dereference_protected()22Monitor
- ← EarlierCVE-2024-40995Jul 12, 2024 · net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc()22Monitor
- Later →CVE-2024-40999Jul 12, 2024 · net: ena: Add validation for completion descriptors consistency22Monitor
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 | 1e2df0ee0afd6d4b436a740f04f7a759e6531005 | Vendor (CNA) |
| Linux Linux | 23afcd52af06880c6c913a0ad99022b8937b575c | Vendor (CNA) |
| Linux Linux | 645267906944a9aeec9d5c56ee24a9096a288798 | Vendor (CNA) |
| Linux Linux | b4b4fda34e535756f9e774fb2d09c4537b7dfd1c | Vendor (CNA) |
| almalinux:bpftool | 7.3.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.42.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.9.7-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseos | Package registry (OSV) |
| rocky linux:kernel | 0:5.14.0-427.42.1.el9_4 · Rocky Linux:9 | 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-50302130 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2024-47685101 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2024-3689843 days apartgpiolib: cdev: fix uninitialised kfifo31Monitor
- CVE-2021-4755349 days apartsched/scs: Reset task stack state in bringup_cpu()31Monitor
- CVE-2024-2702272 days apartfork: defer linking file vma until vma is fully initialized31Monitor
- CVE-2024-50143118 days apartudf: fix uninit-value use in udf_get_fileshortad31Monitor
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0942 · Jul 16, 2024(Linux Kernel Güncellemesi)
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-908 · Use of Uninitialized ResourceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.