Local kernel crash via unflushed SLCAN work
Published Oct 21, 2024 · Updated May 11, 2026
A NULL pointer dereference in Linux 6.0 through 6.0.12 allows local users to crash the kernel through the SLCAN TTY interface. slcan_close() frees the SLCAN transmit-work structure without flushing scheduled tx_work, leaving a kernel worker to dereference freed state. Reachability requires local access to feed bytes into an SLCAN TTY and force a write wakeup while its network device was never brought up; the result is a host-level kernel crash.
Summary
What happened
A NULL pointer dereference in Linux 6.0 through 6.0.12 allows local users to crash the kernel through the SLCAN TTY interface. slcan_close() frees the SLCAN transmit-work structure without flushing scheduled tx_work, leaving a kernel worker to dereference freed state. Reachability requires local access to feed bytes into an SLCAN TTY and force a write wakeup while its network device was never brought up; the result is a host-level kernel crash.
The record
- CVE
- CVE-2022-48984
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 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.0
- Affected versionversion=cfcb4465e9923bb9ac168abcea84e880633f9cef <9e2709d58a14a10eb00d919acd7dec071c33f8c8
- Affected versionversion=cfcb4465e9923bb9ac168abcea84e880633f9cef <fb855e9f3b6b42c72af3f1eb0b288998fe0d5ebb
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