Kernel memory leak and use-after-free via concurrent lseek
Published Oct 21, 2024 · Updated Aug 5, 2026
A race condition in the Linux btrfs implementation allows local users to leak kernel memory via concurrent lseek calls. In find_desired_extent(), threads sharing one file descriptor can both observe a null private_data pointer, allocate separate private structures, and overwrite the same pointer. The trigger requires SEEK_DATA or SEEK_HOLE calls from the same process; shared cached state can subsequently be freed while another thread still uses it.
Summary
What happened
A race condition in the Linux btrfs implementation allows local users to leak kernel memory via concurrent lseek calls. In find_desired_extent(), threads sharing one file descriptor can both observe a null private_data pointer, allocate separate private structures, and overwrite the same pointer. The trigger requires SEEK_DATA or SEEK_HOLE calls from the same process; shared cached state can subsequently be freed while another thread still uses it.
The record
- CVE
- CVE-2024-47741
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 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=3c32c7212f1639471ec0197ff1179b8ef2e0f3d3 <33d1310d4496e904123dab9c28b2d8d2c1800f97
- Affected versionversion=3c32c7212f1639471ec0197ff1179b8ef2e0f3d3 <7ee85f5515e86a4e2a2f51969795920733912bad
- Affected versionversion=3c32c7212f1639471ec0197ff1179b8ef2e0f3d3 <a412ca489ac27b9d0e603499315b7139c948130d
- Affected versionversion=3c32c7212f1639471ec0197ff1179b8ef2e0f3d3 <f56a6d9c267ec7fa558ede7755551c047b1034cd
- Affected versionversion=6.2
What conditions does exploitation require?
What is affected?
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