CVE-2024-41012: filelock: Remove locks reliably when fcntl/close race is detected
Noroxi assessment
Priority: Monitor (action score 25/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.23% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 3cad1bc010416c6dd780643476bc59ed742436b9, 52c87ab18c76c14d7209646ccb3283b3f5d87b22, 5661b9c7ec189406c2dde00837aaa4672efb6240.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 3cad1bc010416c6dd780643476bc59ed742436b9, 52c87ab18c76c14d7209646ccb3283b3f5d87b22, 5661b9c7ec189406c2dde00837aaa4672efb6240 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: filelock: Remove locks reliably when fcntl/close race is detected When fcntl_setlk() races with close(), it removes the created lock with do_lock_file_wait(). However, LSMs can allow the first do_lock_file_wait() that created the lock while denying the second do_lock_file_wait() that tries to remove the lock. Separately, posix_lock_file() could also fail to remove a lock due to GFP_KERNEL allocation failure (when splitting a range in the middle). After the bug has been triggered, use-after-free reads will occur in lock_get_status() when userspace reads /proc/locks. This can likely be used to read arbitrary kernel memory, but can't corrupt kernel memory. Fix it by calling locks_remove_posix() instead, which is designed to reliably get rid of POSIX locks associated with the given file and files_struct and is also used by filp_flush().
- Published
- Jul 23, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-416
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 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
- 6.3
- CNA · Linux
- 7.8
- 1.5 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.13 and later · before 4.19.319
- linux linux kernel4.20 and later · before 5.4.281
- linux linux kernel5.5 and later · before 5.10.223
- linux linux kernel5.11 and later · before 5.15.164
- linux linux kernel5.16 and later · before 6.1.101
- linux linux kernel6.2 and later · before 6.6.42
- linux linux kernel6.7 and later · before 6.9.9
- linux linux kernel6.10
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
- 2.6.13affected
- c293621bbf678a3d85e3ed721c3921c8a670610d and later · before d30ff33040834c3b9eee29740acd92f9c7ba2250affected · git
- c293621bbf678a3d85e3ed721c3921c8a670610d and later · before dc2ce1dfceaa0767211a9d963ddb029ab21c4235affected · git
- c293621bbf678a3d85e3ed721c3921c8a670610d and later · before 5661b9c7ec189406c2dde00837aaa4672efb6240affected · git
- c293621bbf678a3d85e3ed721c3921c8a670610d and later · before 52c87ab18c76c14d7209646ccb3283b3f5d87b22affected · git
- c293621bbf678a3d85e3ed721c3921c8a670610d and later · before ef8fc41cd6f95f9a4a3470f085aecf350569a0b3affected · git
- c293621bbf678a3d85e3ed721c3921c8a670610d and later · before 5f5d0799eb0a01d550c21b7894e26b2d9db55763affected · git
- c293621bbf678a3d85e3ed721c3921c8a670610d and later · before b6d223942c34057fdfd8f149e763fa823731b224affected · git
- c293621bbf678a3d85e3ed721c3921c8a670610d and later · before 3cad1bc010416c6dd780643476bc59ed742436b9affected · git
- before 2.6.13not 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:11 | linux | before 5.10.223-1 | 5.10.223-1 |
| Debian:12 | linux | before 6.1.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.9.9-1 | 6.9.9-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-41010Jul 17, 2024 · bpf: Fix too early release of tcx_entry22Monitor
- ← EarlierCVE-2024-41011Jul 18, 2024 · drm/amdkfd: don't allow mapping the MMIO HDP page with large pages31Monitor
- Later →CVE-2024-41013Jul 29, 2024 · xfs: don't walk off the end of a directory data block28Monitor
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 | 3cad1bc010416c6dd780643476bc59ed742436b9 | Vendor (CNA) |
| Linux Linux | 52c87ab18c76c14d7209646ccb3283b3f5d87b22 | Vendor (CNA) |
| Linux Linux | 5661b9c7ec189406c2dde00837aaa4672efb6240 | Vendor (CNA) |
| Linux Linux | 5f5d0799eb0a01d550c21b7894e26b2d9db55763 | Vendor (CNA) |
| Linux Linux | b6d223942c34057fdfd8f149e763fa823731b224 | Vendor (CNA) |
| Linux Linux | d30ff33040834c3b9eee29740acd92f9c7ba2250 | Vendor (CNA) |
| Linux Linux | dc2ce1dfceaa0767211a9d963ddb029ab21c4235 | Vendor (CNA) |
| Linux Linux | ef8fc41cd6f95f9a4a3470f085aecf350569a0b3 | Vendor (CNA) |
| debian:linux | 6.1.106-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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1050 · Jul 24, 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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/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/52c87ab18c76c14d7209646ccb3283b3f5d87b22
- git.kernel.org/stable/c/5661b9c7ec189406c2dde00837aaa4672efb6240
- git.kernel.org/stable/c/5f5d0799eb0a01d550c21b7894e26b2d9db55763
- git.kernel.org/stable/c/b6d223942c34057fdfd8f149e763fa823731b224
- git.kernel.org/stable/c/d30ff33040834c3b9eee29740acd92f9c7ba2250
- git.kernel.org/stable/c/dc2ce1dfceaa0767211a9d963ddb029ab21c4235
- git.kernel.org/stable/c/ef8fc41cd6f95f9a4a3470f085aecf350569a0b3
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.