# CVE-2026-98751: tty: abort break signalling on hangup

> A race condition in Linux kernel TTY break signaling allows local attackers to trigger a denial of service by racing hangup with break ioctls.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-108975, BELL-CVE-2026-98751, DEBIAN-CVE-2026-98751, GHSA-cg92-2wfv-ppg3, UBUNTU-CVE-2026-98751

## What is CVE-2026-98751?

CVE-2026-98751 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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).

## Which versions are affected by CVE-2026-98751?


## How do I fix CVE-2026-98751?

Apply the vendor's patch.

## Is CVE-2026-98751 being exploited?

There is no known exploitation of CVE-2026-98751 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98751 and fix it if it is affected.

What it is: CVE-2026-98751 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98751 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98751/ (Markdown: https://insights.sbomify.com/CVE-2026-98751/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98751
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98751
- OSV: https://osv.dev/vulnerability/CVE-2026-98751

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98751/
Summaries are generated and may contain mistakes; the official description above is the record.