System crash via uninitialized Speakup synthesizer dereference
Published May 13, 2021 · Updated Aug 4, 2024
NULL pointer dereference in Linux Kernel 5.9.11 allows local users to crash the system through the Speakup line discipline. The spk_ttyio_receive_buf2() callback dereferences spk_ttyio_synth after user space selects the exposed line discipline, without verifying that the synthesizer pointer is initialized. A local account with access to /dev/tty1 and the required TTY ioctls can trigger a kernel panic; the published reproduction enabled accessibility, Speakup, and KASAN.
Summary
What happened
NULL pointer dereference in Linux Kernel 5.9.11 allows local users to crash the system through the Speakup line discipline. The spk_ttyio_receive_buf2() callback dereferences spk_ttyio_synth after user space selects the exposed line discipline, without verifying that the synthesizer pointer is initialized. A local account with access to /dev/tty1 and the required TTY ioctls can trigger a kernel panic; the published reproduction enabled accessibility, Speakup, and KASAN.
The record
- CVE
- CVE-2020-27830
- Published
- May 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=kernel 5.9.14
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
- Speakup line-discipline ioctl proof of conceptproof of concept · demonstrated
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