Kernel crash via stale tty link reference
Published May 8, 2026 · Updated May 8, 2026
Use-after-free in the Linux Kernel CAIF serial driver allows local users to crash the kernel through line-discipline activity. The caif_serial TX path calls tty_write_room() after tty->link can be freed, causing pty_write_room() to dereference the stale tty->link->port pointer. Reachability requires CAP_SYS_ADMIN or CAP_SYS_TTY_CONFIG in the initial user namespace; successful triggering interrupts the host through a kernel crash.
Summary
What happened
Use-after-free in the Linux Kernel CAIF serial driver allows local users to crash the kernel through line-discipline activity. The caif_serial TX path calls tty_write_room() after tty->link can be freed, causing pty_write_room() to dereference the stale tty->link->port pointer. Reachability requires CAP_SYS_ADMIN or CAP_SYS_TTY_CONFIG in the initial user namespace; successful triggering interrupts the host through a kernel crash.
The record
- CVE
- CVE-2026-43458
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 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.35
- Affected versionversion=e31d5a05948e4478ba8396063d1e1f39880928e2 <23a3ac2e2262a291498567418227b99e1f3606b1
- Affected versionversion=e31d5a05948e4478ba8396063d1e1f39880928e2 <27e43356d0defb9fc7fa25265219a3ffeb7b3e98
- Affected versionversion=e31d5a05948e4478ba8396063d1e1f39880928e2 <288598d80a068a0e9281de35bcb4ce495f189e2a
- Affected versionversion=e31d5a05948e4478ba8396063d1e1f39880928e2 <35b58d3bc716ebb9ebd10fe1cac8c1177242511c
- Affected versionversion=e31d5a05948e4478ba8396063d1e1f39880928e2 <52135420e9f75853ea0c6cea7b736e3e98495f7d
- Affected versionversion=e31d5a05948e4478ba8396063d1e1f39880928e2 <8460187b4852fd00bd1c76394358053f3fa4d089
- Affected versionversion=e31d5a05948e4478ba8396063d1e1f39880928e2 <97a0bb491cae39478c6225381f14e9ac67b7bba7
- Affected versionversion=e31d5a05948e4478ba8396063d1e1f39880928e2 <ca2ceba983bb23ea0202c2882d963253416654a3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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