Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98753tty: tty_port: restore TTY_IO_ERROR on activation failure

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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected a9a37ec33a1b3e66b260ac1c29bff0aec8b89ae4 – < 761e8c5eb13d1b5e196b0b39bdfed6fc67af9dd2
    • affected a9a37ec33a1b3e66b260ac1c29bff0aec8b89ae4 – < 5469dc4153a60289c5bae00215947c6ce09fcc0e
    • affected a9a37ec33a1b3e66b260ac1c29bff0aec8b89ae4 – < e24625bff786fa3f22cc38b5038362b910621e83
    • affected a9a37ec33a1b3e66b260ac1c29bff0aec8b89ae4 – < 16032c980d8f71642fcdc99309c571df3fcf3328
    • affected a9a37ec33a1b3e66b260ac1c29bff0aec8b89ae4 – < 34d4f67472ef7a744970b772a8565ddc727788e2
    • affected a9a37ec33a1b3e66b260ac1c29bff0aec8b89ae4 – < 7021acc84c2e0add77a1a33152e3a1e428fdbfdb
    • affected a9a37ec33a1b3e66b260ac1c29bff0aec8b89ae4 – < 6388409b711eb91b14fa075a4d861ccc4df1cfe7
    • affected a9a37ec33a1b3e66b260ac1c29bff0aec8b89ae4 – < 56964f6a31238fb41d5830bb42520c5b10ff7d8f
  • Linux · Linux

    • affected 2.6.33
    • unaffected < 2.6.33
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98753 badge
[![CVE-2026-98753](https://cveledger.app/badge/CVE-2026-98753.svg)](https://cveledger.app/cve/CVE-2026-98753)

Record last updated .