Kernel crash via AX.25 teardown race
Published Aug 29, 2022 · Updated Apr 23, 2025
Null pointer dereference and use-after-free in Linux Kernel before 5.18-rc4 allow remote attackers to crash the kernel via AX.25 amateur-radio traffic. The net/ax25/af_ax25.c teardown path races ax25_disconnect() with ax25_destroy_socket(), allowing ax25->sk to become NULL or freed while dereferenced. Exploitation requires AX.25 protocol activity and causes denial of service; no confidentiality or integrity impact is reported.
Summary
What happened
Null pointer dereference and use-after-free in Linux Kernel before 5.18-rc4 allow remote attackers to crash the kernel via AX.25 amateur-radio traffic. The net/ax25/af_ax25.c teardown path races ax25_disconnect() with ax25_destroy_socket(), allowing ax25->sk to become NULL or freed while dereferenced. Exploitation requires AX.25 protocol activity and causes denial of service; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2022-1199
- Published
- Aug 29, 2022
- Updated
- Apr 23, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, CWE-416, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=Fixed in kernel v5.18-rc4
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.
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