Local kernel crash via oversized Speakup word
Published May 1, 2024 · Updated Aug 5, 2026
Buffer overrun in Linux Speakup from 2.6.37 allows local users to crash the kernel by placing a word longer than 256 characters on a large console. The word-scanning logic in drivers/accessibility/speakup/main.c advances through console text without stopping before its fixed word buffer is exhausted. The condition requires local control of an unusually large console and long uninterrupted text; triggering it interrupts the running system.
Summary
What happened
Buffer overrun in Linux Speakup from 2.6.37 allows local users to crash the kernel by placing a word longer than 256 characters on a large console. The word-scanning logic in drivers/accessibility/speakup/main.c advances through console text without stopping before its fixed word buffer is exhausted. The condition requires local control of an unusually large console and long uninterrupted text; triggering it interrupts the running system.
The record
- CVE
- CVE-2024-26994
- Published
- May 1, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 1, 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=2.6.37
- Affected versionversion=c6e3fd22cd538365bfeb82997d5b89562e077d42 <0d130158db29f5e0b3893154908cf618896450a8
- Affected versionversion=c6e3fd22cd538365bfeb82997d5b89562e077d42 <0efb15c14c493263cb3a5f65f5ddfd4603d19a76
- Affected versionversion=c6e3fd22cd538365bfeb82997d5b89562e077d42 <6401038acfa24cba9c28cce410b7505efadd0222
- Affected versionversion=c6e3fd22cd538365bfeb82997d5b89562e077d42 <756c5cb7c09e537b87b5d3acafcb101b2ccf394f
- Affected versionversion=c6e3fd22cd538365bfeb82997d5b89562e077d42 <89af25bd4b4bf6a71295f07e07a8ae7dc03c6595
- Affected versionversion=c6e3fd22cd538365bfeb82997d5b89562e077d42 <8defb1d22ba0395b81feb963b96e252b097ba76f
- Affected versionversion=c6e3fd22cd538365bfeb82997d5b89562e077d42 <8f6b62125befe1675446923e4171eac2c012959c
- Affected versionversion=c6e3fd22cd538365bfeb82997d5b89562e077d42 <c8d2f34ea96ea3bce6ba2535f867f0d4ee3b22e1
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