Look up another CVE · open CVE-2026-98753 in the interactive tracker
CVE-2026-98753
tty: tty_port: restore TTY_IO_ERROR on activation failure
Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/tty. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-98753 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.12.113-1 | Update the kernel and reboot. Fixed in 6.12.113-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.10-1 | Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.10-1 | Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
Make sure to restore the TTY_IO_ERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down. This specifically avoids issues like kernel panic due to unclocked accesses or NULL-pointer dereferences when accessing powered down or deregistered ports when a TTY ioctl races with hangup and open. Note that the flag is set again in tty_port_close() but not restoring it on activation failure leaves a window where drivers fail to handle the ioctl-hangup race.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/tty/tty_port.c
- What this is
- TTY LAYER AND SERIAL DRIVERSMAINTAINERS section matched on drivers/tty/ · linux-kernel@vger.kernel.org · Supported
Check it on the machine
grep -w CONFIG_TTY /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this code. Every release below compiles the affected file into the kernels it ships.
- bookworm, trixie, forky, sidy
- y
- built into the kernel image on every flavour - only a patch removes it
- Build switch
- CONFIG_TTY
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-10-18 (today)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- not scored
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/tty
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 2.6.33 | 6.12.113 | 34d4f67472ef |
| 2.6.33 | 6.18.56 | 7021acc84c2e |
| 2.6.33 | 7.2.10 | 6388409b711e |
| 2.6.33 | 7.3 | 56964f6a3123 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98753, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.