Kernel memory corruption via namespace teardown race
Published Oct 21, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux kernel allows local users to corrupt kernel memory during network namespace teardown. During namespace dismantling, dst_release() defers dst_destroy() past an RCU grace period, so dst_entries_add() can access per-CPU state already freed by dst_entries_destroy(). The flaw requires local low-privileged access and timing the teardown race, with kernel crashes or memory compromise as bounded consequences.
Summary
What happened
Use-after-free in the Linux kernel allows local users to corrupt kernel memory during network namespace teardown. During namespace dismantling, dst_release() defers dst_destroy() past an RCU grace period, so dst_entries_add() can access per-CPU state already freed by dst_entries_destroy(). The flaw requires local low-privileged access and timing the teardown race, with kernel crashes or memory compromise as bounded consequences.
The record
- CVE
- CVE-2024-50036
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- 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=3.10.50 <3.11
- Affected versionversion=3.12.26 <3.13
- Affected versionversion=3.14.14 <3.15
- Affected versionversion=3.15.7 <3.16
- Affected versionversion=3.16
- Affected versionversion=591b1e1bb40152e22cee757f493046a0ca946bf8
- Affected versionversion=86e48c03d774e01ccd71ecba4fc4b5c2bc0b5b41
- Affected versionversion=9a4fe697023dbe6c25caa1f8b2153af869a29bd2
- Affected versionversion=df90819dafcd6b97fc665f63a15752a570e227a2
- Affected versionversion=f88649721268999bdff09777847080a52004f691 <3c7c918ec0aa3555372c5a57f18780b7a96c5cfc
- Affected versionversion=f88649721268999bdff09777847080a52004f691 <547087307bc19417b4f2bc85ba9664a3e8db5a6a
- Affected versionversion=f88649721268999bdff09777847080a52004f691 <a60db84f772fc3a906c6c4072f9207579c41166f
- Affected versionversion=f88649721268999bdff09777847080a52004f691 <ac888d58869bb99753e7652be19a151df9ecb35d
- Affected versionversion=f88649721268999bdff09777847080a52004f691 <e3915f028b1f1c37e87542e5aadd33728c259d96
- Affected versionversion=f88649721268999bdff09777847080a52004f691 <eae7435b48ffc8e9be0ff9cfeae40af479a609dd
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