CVE-2026-98752: tty: port: fix tty_port_tty_vhangup() 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 017b18addbe8dcace1a569a00d40ed1ba1e03f4c, 2.6.32, 2e16ae1464a4f435425c6f6ff1e293db850a624c; 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 Release Notes.
Low priority for now. Upgrade to Linux Linux 017b18addbe8dcace1a569a00d40ed1ba1e03f4c, 2.6.32, 2e16ae1464a4f435425c6f6ff1e293db850a624c; 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 Release Notes 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: port: fix tty_port_tty_vhangup() race Drivers rely on tty_port_tty_vhangup() to synchronously hang up their ports before tearing down resources as part of deregistration (e.g. on physical disconnect). If tty_port_tty_vhangup() races with another hangup it may however return before the port has been shut down. This is in turn can lead to use-after-free and NULL-pointer dereferences in racing ioctls (including a synchronous hangup) and in processing of racing asynchronous hangups (carrier loss). Add the missing serialisation to tty_port_tty_vhangup() and tty_port_hangup() so that the former does not return until the port has been shut down also when there is a racing hangup. Note that serial core does not use tty_port_hangup(), but it already holds the port mutex when clearing port->tty and shutting down the port in uart_hangup().
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 4260dc792fabfd20c8644fa9414b2ae48372365f, 2.6.32affected
- 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e and later · before a78910f6d78cc1415cbc9b4fb621c3f4f6945be2affected · git
- 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e and later · before 2e16ae1464a4f435425c6f6ff1e293db850a624caffected · git
- 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e and later · before a776d603d1e1bba2837295817b0a39394707b10daffected · git
- 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e and later · before ce220b4cdf62f73db0c1940f968eb33b9899fdd0affected · git
- 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e and later · before 6d1a984afc3ca477dab3e51ec806671d443ad524affected · git
- 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e and later · before 6b7be3b9b857947e9c1338d4919d4ebd3b75e907affected · git
- 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e and later · before 017b18addbe8dcace1a569a00d40ed1ba1e03f4caffected · git
- 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e and later · before b48820de8c1a596c5b99775524dfce73c6576c5daffected · git
- 2.6.31.2 and later · before 2.6.32affected · 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-98750Oct 18, 2026 · tty: fix saved termios reset race0Monitor
- ← EarlierCVE-2026-98751Oct 18, 2026 · tty: abort break signalling on hangup0Monitor
- Later →CVE-2026-98753Oct 18, 2026 · tty: tty_port: restore TTY_IO_ERROR on activation failure0Monitor
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 | 017b18addbe8dcace1a569a00d40ed1ba1e03f4c | Vendor (CNA) |
| Linux Linux | 2.6.32 | Vendor (CNA) |
| Linux Linux | 2e16ae1464a4f435425c6f6ff1e293db850a624c | Vendor (CNA) |
| Linux Linux | 6b7be3b9b857947e9c1338d4919d4ebd3b75e907 | Vendor (CNA) |
| Linux Linux | 6d1a984afc3ca477dab3e51ec806671d443ad524 | Vendor (CNA) |
| Linux Linux | a776d603d1e1bba2837295817b0a39394707b10d | Vendor (CNA) |
| Linux Linux | a78910f6d78cc1415cbc9b4fb621c3f4f6945be2 | Vendor (CNA) |
| Linux Linux | b48820de8c1a596c5b99775524dfce73c6576c5d | Vendor (CNA) |
| Linux Linux | ce220b4cdf62f73db0c1940f968eb33b9899fdd0 | 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 | 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 6, 2026+19 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- 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/2e16ae1464a4f435425c6f6ff1e293db850a624c
- git.kernel.org/stable/c/6b7be3b9b857947e9c1338d4919d4ebd3b75e907
- git.kernel.org/stable/c/6d1a984afc3ca477dab3e51ec806671d443ad524
- git.kernel.org/stable/c/a776d603d1e1bba2837295817b0a39394707b10d
- git.kernel.org/stable/c/a78910f6d78cc1415cbc9b4fb621c3f4f6945be2
- git.kernel.org/stable/c/b48820de8c1a596c5b99775524dfce73c6576c5d
- git.kernel.org/stable/c/ce220b4cdf62f73db0c1940f968eb33b9899fdd0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.