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-98750tty: fix saved termios reset race

Description

In the Linux kernel, the following vulnerability has been resolved: tty: fix saved termios reset race Resetting saved termios state on device registration is needed where a minor number can be reused for an entirely different device and where the old settings may prevent the port from even being opened (e.g. when CLOCAL is not set). Not all TTY drivers guarantee that the minor number is no longer in use when registering devices however, something which can lead to a use-after-free when closing a TTY (and saving its termios) races with re-registration. Add a new TTY_DRIVER_RESET_SAVED_TERMIOS flag to request that any saved termios state is reset on registration and only set it for drivers that make sure that the minor number is no longer in use.

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 (18 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 93857edd9829e144acb6c7e72d593f6e01aead66 – < 15ddaf908a8eee14e1872ff9c4cdb73562634e7e
    • affected 93857edd9829e144acb6c7e72d593f6e01aead66 – < bcb9b5df70d439f3c9d5a2d7f359dd7ab117bee0
    • affected 93857edd9829e144acb6c7e72d593f6e01aead66 – < 33048616c4e22930e8769b8d14ee8a0dc5a80ceb
    • affected 93857edd9829e144acb6c7e72d593f6e01aead66 – < 6b4e15cccfbe03b7c6ae60ff570c401bfb1e51d6
    • affected 93857edd9829e144acb6c7e72d593f6e01aead66 – < 1572d86bcf0bcb848d20fc5e5de7ed6963034c2b
    • affected 93857edd9829e144acb6c7e72d593f6e01aead66 – < 08bf919f041af9de372428bb0c938157ea144164
    • affected 93857edd9829e144acb6c7e72d593f6e01aead66 – < dcaf0251f847a45861e94c6617024a9455687d2f
    • affected 93857edd9829e144acb6c7e72d593f6e01aead66 – < 8df07fe93573e9e548d6645273e9bcb6eb74059e
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • 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-98750 badge
[![CVE-2026-98750](https://cveledger.app/badge/CVE-2026-98750.svg)](https://cveledger.app/cve/CVE-2026-98750)

Record last updated .