Kernel crash via line-discipline teardown race
Published Jun 18, 2020 · Updated Aug 4, 2024
Use-after-free in Linux kernel SLIP and SLCAN before 5.4.16 allows local users to crash the system during line-discipline teardown. The write_wakeup handlers read tty->disc_data and schedule work while close can clear the pointer and free its network device, leaving the handlers to dereference freed memory. Exploitation requires privileged local access, a configured SLIP or SLCAN line discipline, and a race between write wakeup and close.
Summary
What happened
Use-after-free in Linux kernel SLIP and SLCAN before 5.4.16 allows local users to crash the system during line-discipline teardown. The write_wakeup handlers read tty->disc_data and schedule work while close can clear the pointer and free its network device, leaving the handlers to dereference freed memory. Exploitation requires privileged local access, a configured SLIP or SLCAN line discipline, and a race between write wakeup and close.
The record
- CVE
- CVE-2020-14416
- Published
- Jun 18, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, CWE-362
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 18, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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