Kernel use-after-free via unlocked tracepoint
Published Jul 29, 2024 · Updated Aug 5, 2026
Use-after-free in Linux kernel file locking allows local users to trigger unsafe kernel memory access during concurrent POSIX lock operations. In posix_lock_inode, request can point to a lock-list entry that another task frees before trace_posix_lock_inode reads it because the tracepoint runs after flc_lock is released. Triggering requires local low-privileged access and a concurrent lock race; the public record demonstrates a KASAN fault but does not establish a reliable exploit consequence.
Summary
What happened
Use-after-free in Linux kernel file locking allows local users to trigger unsafe kernel memory access during concurrent POSIX lock operations. In posix_lock_inode, request can point to a lock-list entry that another task frees before trace_posix_lock_inode reads it because the tracepoint runs after flc_lock is released. Triggering requires local low-privileged access and a concurrent lock race; the public record demonstrates a KASAN fault but does not establish a reliable exploit consequence.
The record
- CVE
- CVE-2024-41049
- Published
- Jul 29, 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 29, 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=117fb80cd1e63c419c7a221ce070becb4bfc7b6d <1cbbb3d9475c403ebedc327490c7c2b991398197
- Affected versionversion=34bff6d850019e00001129d6de3aa4874c2cf471 <5cb36e35bc10ea334810937990c2b9023dacb1b0
- Affected versionversion=5.10.197 <5.10.222
- Affected versionversion=5.15.133 <5.15.163
- Affected versionversion=5.4.257 <5.4.280
- Affected versionversion=6.1.55 <6.1.100
- Affected versionversion=6.5.5 <6.6
- Affected versionversion=6.6
- Affected versionversion=74f6f5912693ce454384eaeec48705646a21c74f <116599f6a26906cf33f67975c59f0692ecf7e9b2
- Affected versionversion=74f6f5912693ce454384eaeec48705646a21c74f <1b3ec4f7c03d4b07bad70697d7e2f4088d2cfe92
- Affected versionversion=74f6f5912693ce454384eaeec48705646a21c74f <432b06b69d1d354a171f7499141116536579eb6a
- Affected versionversion=766e56faddbec2eaf70c9299e1c9ef74d846d32b <02a8964260756c70b20393ad4006948510ac9967
- Affected versionversion=a6f4129378ca15f62cbdde09a7d3ccc35adcf49d <7d4c14f4b511fd4c0dc788084ae59b4656ace58b
- Affected versionversion=e75396988bb9b3b90e6e8690604d0f566cea403a
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