System crash via racy VMA locking
Published Feb 8, 2024 · Updated Aug 1, 2024
Use-after-free in the Linux kernel before 6.5-rc4 allows local users to crash the system by racing virtual-memory-area operations. The lock_vma_under_rcu function tests vma->anon_vma before taking the VMA lock, so concurrent move_vma and unlink_anon_vmas operations can detach it and leave the page-fault path using freed memory. Successful exploitation requires a local user to win two races; the bounded consequence is a kernel crash and service interruption.
Summary
What happened
Use-after-free in the Linux kernel before 6.5-rc4 allows local users to crash the system by racing virtual-memory-area operations. The lock_vma_under_rcu function tests vma->anon_vma before taking the VMA lock, so concurrent move_vma and unlink_anon_vmas operations can detach it and leave the page-fault path using freed memory. Successful exploitation requires a local user to win two races; the bounded consequence is a kernel crash and service interruption.
The record
- CVE
- CVE-2024-1312
- Published
- Feb 8, 2024
- Updated
- Aug 1, 2024
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
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