Local privilege escalation via mismatched AX.25 tracker release
Published May 20, 2024 · Updated Aug 5, 2026
Memory corruption in Linux kernel AX.25 networking allows local users to escalate privileges through device-detachment processing. In ax25_kill_by_device(), detachment releases ax25_dev->dev_tracker instead of the tracker stored in the bound ax25_cb, causing a stale tracker to be released again. An unprivileged local user must bind an AX.25 socket before its device goes down or detaches; the resulting kernel memory corruption permits disclosure, code execution, or a crash.
Summary
What happened
Memory corruption in Linux kernel AX.25 networking allows local users to escalate privileges through device-detachment processing. In ax25_kill_by_device(), detachment releases ax25_dev->dev_tracker instead of the tracker stored in the bound ax25_cb, causing a stale tracker to be released again. An unprivileged local user must bind an AX.25 socket before its device goes down or detaches; the resulting kernel memory corruption permits disclosure, code execution, or a crash.
The record
- CVE
- CVE-2024-36009
- Published
- May 20, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 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.14.277 <4.15
- Affected versionversion=4.19.240 <4.20
- Affected versionversion=5.10.112 <5.11
- Affected versionversion=5.15.35 <5.16
- Affected versionversion=5.17
- Affected versionversion=5.4.190 <5.5
- Affected versionversion=57cc15f5fd550316e4104eaf84b90fbc640fd7a5
- Affected versionversion=7528d0f2210c3a1154186175516ed37aa970f2b1
- Affected versionversion=b1e0a6fc7f17500484c402ad1cd018c24dfc14b3
- Affected versionversion=b8c07f33aa35dacf5444e7053ed9662d1869f536
- Affected versionversion=b982492ec3a115e0a136856a1b2dbe32f2d21a0e
- Affected versionversion=feef318c855a361a1eccd880f33e88c460eb63b4 <0d14f104027e30720582448706c7d6b43065c851
- Affected versionversion=feef318c855a361a1eccd880f33e88c460eb63b4 <467324bcfe1a31ec65d0cf4aa59421d6b7a7d52b
- Affected versionversion=feef318c855a361a1eccd880f33e88c460eb63b4 <4fee8fa86a15d7790268eea458b1aec69c695530
- Affected versionversion=feef318c855a361a1eccd880f33e88c460eb63b4 <c42b073d9af4a5329b25b17390c63ab3847f30e8
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