Answer in brief
CVE-2026-98752 records a Unknown severity vulnerability in tty: port: fix tty_port_tty_vhangup() race. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <6d1a984afc3ca477dab3e51ec806671d443ad524 || >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <6b7be3b9b857947e9c1338d4919d4ebd3b75e907 || >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <017b18addbe8dcace1a569a00d40ed1ba1e03f4c || >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <b48820de8c1a596c5b99775524dfce73c6576c5d || 4260dc792fabfd20c8644fa9414b2ae48372365f || >=2.6.31.2 <2.6.32 | 6d1a984afc3ca477dab3e51ec806671d443ad524, 6b7be3b9b857947e9c1338d4919d4ebd3b75e907, 017b18addbe8dcace1a569a00d40ed1ba1e03f4c, b48820de8c1a596c5b99775524dfce73c6576c5d, 2.6.32 |
| Linux/Linuxgeneric | 2.6.32 | Not reported |
| Linux/Linuxgeneric | >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <ce220b4cdf62f73db0c1940f968eb33b9899fdd0 || >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <6d1a984afc3ca477dab3e51ec806671d443ad524 || >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <6b7be3b9b857947e9c1338d4919d4ebd3b75e907 || >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <017b18addbe8dcace1a569a00d40ed1ba1e03f4c || >=7ca0ff9ab3218ec443a7a9ad247e4650373ed41e <b48820de8c1a596c5b99775524dfce73c6576c5d || 4260dc792fabfd20c8644fa9414b2ae48372365f || >=2.6.31.2 <2.6.32 | ce220b4cdf62f73db0c1940f968eb33b9899fdd0, 6d1a984afc3ca477dab3e51ec806671d443ad524, 6b7be3b9b857947e9c1338d4919d4ebd3b75e907, 017b18addbe8dcace1a569a00d40ed1ba1e03f4c, b48820de8c1a596c5b99775524dfce73c6576c5d, 2.6.32 |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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().
Quoted source text, attributed separately from HOL analysis.