# CVE-2026-98750: tty: fix saved termios reset race

> A race condition in the Linux kernel TTY subsystem allows local attackers to trigger a use-after-free, potentially leading to privilege escalation or code execution.

- **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-109170, BELL-CVE-2026-98750, DEBIAN-CVE-2026-98750, GHSA-447r-jv65-jrgx, UBUNTU-CVE-2026-98750

## What is CVE-2026-98750?

CVE-2026-98750 is an use after free 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: 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.

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


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

Apply the vendor's patch.

## Is CVE-2026-98750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98750 is an use after free 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-98750 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-98750/ (Markdown: https://insights.sbomify.com/CVE-2026-98750/index.md)
```

## Sources

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

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