Kernel crash via unsynchronized memcg ID removal
Published Aug 26, 2024 · Updated Aug 5, 2026
Race condition in affected Linux kernel branches allows local users to crash the system during concurrent memory-cgroup teardown. The memcg teardown path calls idr_remove() on mem_cgroup_idr without cgroup_mutex, allowing concurrent modifications to corrupt ID assignments. Low-privileged local access and a difficult race are required; duplicate IDs can remove another cgroup's list_lru state and crash the kernel.
Summary
What happened
Race condition in affected Linux kernel branches allows local users to crash the system during concurrent memory-cgroup teardown. The memcg teardown path calls idr_remove() on mem_cgroup_idr without cgroup_mutex, allowing concurrent modifications to corrupt ID assignments. Low-privileged local access and a difficult race are required; duplicate IDs can remove another cgroup's list_lru state and crash the kernel.
The record
- CVE
- CVE-2024-43892
- Published
- Aug 26, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 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=4.4.18 <4.5
- Affected versionversion=4.6.6 <4.7
- Affected versionversion=4.7
- Affected versionversion=73f576c04b9410ed19660f74f97521bee6e1c546 <37a060b64ae83b76600d187d76591ce488ab836b
- Affected versionversion=73f576c04b9410ed19660f74f97521bee6e1c546 <51c0b1bb7541f8893ec1accba59eb04361a70946
- Affected versionversion=73f576c04b9410ed19660f74f97521bee6e1c546 <56fd70f4aa8b82199dbe7e99366b1fd7a04d86fb
- Affected versionversion=73f576c04b9410ed19660f74f97521bee6e1c546 <912736a0435ef40e6a4ae78197ccb5553cb80b05
- Affected versionversion=73f576c04b9410ed19660f74f97521bee6e1c546 <9972605a238339b85bd16b084eed5f18414d22db
- Affected versionversion=73f576c04b9410ed19660f74f97521bee6e1c546 <e6cc9ff2ac0b5df9f25eb790934c3104f6710278
- Affected versionversion=8627c7750a66a46d56d3564e1e881aa53764497c
- Affected versionversion=db70cd18d3da727a3a59694de428a9e41c620de7
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