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-98751

tty: abort break signalling on hangup

Description

In the Linux kernel, the following vulnerability has been resolved: tty: abort break signalling on hangup The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down. Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened). Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the 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 (11 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 f34d7a5b7010b82fe97da95496b9971435530062 – < 70fa2bec352d9f949b882af3c380b916e4a29a43
    • affected f34d7a5b7010b82fe97da95496b9971435530062 – < 8224d25534580d07925607bbd617daf9c8de26c3
    • affected f34d7a5b7010b82fe97da95496b9971435530062 – < 8a0f0f9ef41cb80de4d5da4ae146df3075463f6b
    • affected f34d7a5b7010b82fe97da95496b9971435530062 – < 6c9c9367351a461d62e5c0a39bffdcfbb40f068b
    • affected f34d7a5b7010b82fe97da95496b9971435530062 – < 3bc82999fb85cecc7eb6ec1755ee7d698aa1e783
    • affected f34d7a5b7010b82fe97da95496b9971435530062 – < 94af6cd832e9b4ce39a8fb59144a8f09ab56fd35
    • affected f34d7a5b7010b82fe97da95496b9971435530062 – < c8ccd3b2013daaf77b98f8a6724fcf4d2c5c52d6
    • affected f34d7a5b7010b82fe97da95496b9971435530062 – < 845a2737e0f5ffe5ca8d38de556012b0c9472cdd
  • Linux · Linux

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

Record last updated .