Local kernel warning via incorrect IDR emptiness check
Published Dec 27, 2024 · Updated May 11, 2026
Incorrect IDR state handling in Linux 6.12 through 6.12.1 allows local users to trigger a kernel warning during L2TP namespace teardown. The l2tp_exit_net handler calls idr_is_empty on an IDR whose radix tree can retain only internal nodes after idr_alloc_32 allocation failure, so the check falsely reports live entries before idr_destroy removes those nodes. Reaching the warning requires low-privileged local access, induced allocation failure, and L2TP network-namespace teardown; service interruption depends on a configuration that panics on kernel warnings.
Summary
What happened
Incorrect IDR state handling in Linux 6.12 through 6.12.1 allows local users to trigger a kernel warning during L2TP namespace teardown. The l2tp_exit_net handler calls idr_is_empty on an IDR whose radix tree can retain only internal nodes after idr_alloc_32 allocation failure, so the check falsely reports live entries before idr_destroy removes those nodes. Reaching the warning requires low-privileged local access, induced allocation failure, and L2TP network-namespace teardown; service interruption depends on a configuration that panics on kernel warnings.
The record
- CVE
- CVE-2024-53211
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=6.12
- Affected versionversion=73d33bd063c4cfef3db17f9bec3d202928ed8631 <5d066766c5f1252f98ff859265bcd1a5b52ac46c
- Affected versionversion=73d33bd063c4cfef3db17f9bec3d202928ed8631 <a487cc8986d6dd75b60b59004f3bd2ea9b4dd541
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