Kernel-memory disclosure via unreliably removed POSIX locks
Published Jul 23, 2024 · Updated Aug 5, 2026
Use-after-free in Linux kernel POSIX file locking allows local users to read kernel memory by racing fcntl() against close(). The fcntl_setlk() cleanup path calls do_lock_file_wait(), which can fail after a security-module denial or allocation failure and leave a freed lock visible to lock_get_status(). Exploitation requires local low-privileged code to win the race and then read /proc/locks; the resulting stale reads disclose kernel memory but do not modify it.
Summary
What happened
Use-after-free in Linux kernel POSIX file locking allows local users to read kernel memory by racing fcntl() against close(). The fcntl_setlk() cleanup path calls do_lock_file_wait(), which can fail after a security-module denial or allocation failure and leave a freed lock visible to lock_get_status(). Exploitation requires local low-privileged code to win the race and then read /proc/locks; the resulting stale reads disclose kernel memory but do not modify it.
The record
- CVE
- CVE-2024-41012
- Published
- Jul 23, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.13
- Affected versionversion=c293621bbf678a3d85e3ed721c3921c8a670610d <3cad1bc010416c6dd780643476bc59ed742436b9
- Affected versionversion=c293621bbf678a3d85e3ed721c3921c8a670610d <52c87ab18c76c14d7209646ccb3283b3f5d87b22
- Affected versionversion=c293621bbf678a3d85e3ed721c3921c8a670610d <5661b9c7ec189406c2dde00837aaa4672efb6240
- Affected versionversion=c293621bbf678a3d85e3ed721c3921c8a670610d <5f5d0799eb0a01d550c21b7894e26b2d9db55763
- Affected versionversion=c293621bbf678a3d85e3ed721c3921c8a670610d <b6d223942c34057fdfd8f149e763fa823731b224
- Affected versionversion=c293621bbf678a3d85e3ed721c3921c8a670610d <d30ff33040834c3b9eee29740acd92f9c7ba2250
- Affected versionversion=c293621bbf678a3d85e3ed721c3921c8a670610d <dc2ce1dfceaa0767211a9d963ddb029ab21c4235
- Affected versionversion=c293621bbf678a3d85e3ed721c3921c8a670610d <ef8fc41cd6f95f9a4a3470f085aecf350569a0b3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo