CVE-2026-98750: tty: fix saved termios reset race
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 08bf919f041af9de372428bb0c938157ea144164, 1572d86bcf0bcb848d20fc5e5de7ed6963034c2b, 15ddaf908a8eee14e1872ff9c4cdb73562634e7e; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 08bf919f041af9de372428bb0c938157ea144164, 1572d86bcf0bcb848d20fc5e5de7ed6963034c2b, 15ddaf908a8eee14e1872ff9c4cdb73562634e7e; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- 93857edd9829e144acb6c7e72d593f6e01aead66 and later · before 15ddaf908a8eee14e1872ff9c4cdb73562634e7eaffected · git
- 93857edd9829e144acb6c7e72d593f6e01aead66 and later · before bcb9b5df70d439f3c9d5a2d7f359dd7ab117bee0affected · git
- 93857edd9829e144acb6c7e72d593f6e01aead66 and later · before 33048616c4e22930e8769b8d14ee8a0dc5a80cebaffected · git
- 93857edd9829e144acb6c7e72d593f6e01aead66 and later · before 6b4e15cccfbe03b7c6ae60ff570c401bfb1e51d6affected · git
- 93857edd9829e144acb6c7e72d593f6e01aead66 and later · before 1572d86bcf0bcb848d20fc5e5de7ed6963034c2baffected · git
- 93857edd9829e144acb6c7e72d593f6e01aead66 and later · before 08bf919f041af9de372428bb0c938157ea144164affected · git
- 93857edd9829e144acb6c7e72d593f6e01aead66 and later · before dcaf0251f847a45861e94c6617024a9455687d2faffected · git
- 93857edd9829e144acb6c7e72d593f6e01aead66 and later · before 8df07fe93573e9e548d6645273e9bcb6eb74059eaffected · git
- before 4.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98748Oct 18, 2026 · serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()0Monitor
- ← EarlierCVE-2026-98749Oct 18, 2026 · tty: serial: max3100: shut down timer before freeing port0Monitor
- Later →CVE-2026-98751Oct 18, 2026 · tty: abort break signalling on hangup0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 08bf919f041af9de372428bb0c938157ea144164 | Vendor (CNA) |
| Linux Linux | 1572d86bcf0bcb848d20fc5e5de7ed6963034c2b | Vendor (CNA) |
| Linux Linux | 15ddaf908a8eee14e1872ff9c4cdb73562634e7e | Vendor (CNA) |
| Linux Linux | 33048616c4e22930e8769b8d14ee8a0dc5a80ceb | Vendor (CNA) |
| Linux Linux | 6b4e15cccfbe03b7c6ae60ff570c401bfb1e51d6 | Vendor (CNA) |
| Linux Linux | 8df07fe93573e9e548d6645273e9bcb6eb74059e | Vendor (CNA) |
| Linux Linux | bcb9b5df70d439f3c9d5a2d7f359dd7ab117bee0 | Vendor (CNA) |
| Linux Linux | dcaf0251f847a45861e94c6617024a9455687d2f | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 12, 2026+25 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1572d86bcf0bcb848d20fc5e5de7ed6963034c2b
- git.kernel.org/stable/c/15ddaf908a8eee14e1872ff9c4cdb73562634e7e
- git.kernel.org/stable/c/33048616c4e22930e8769b8d14ee8a0dc5a80ceb
- git.kernel.org/stable/c/6b4e15cccfbe03b7c6ae60ff570c401bfb1e51d6
- git.kernel.org/stable/c/8df07fe93573e9e548d6645273e9bcb6eb74059e
- git.kernel.org/stable/c/bcb9b5df70d439f3c9d5a2d7f359dd7ab117bee0
- git.kernel.org/stable/c/dcaf0251f847a45861e94c6617024a9455687d2f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.