Strix
73.2K

CVE-2026-98752

UnknownEPSS 0.17%

Last modified

CVE-2026-98752 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

Description

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().

Metrics

EPSS Probability
0.17%

6.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e, < a78910f6d78cc1415cbc9b4fb621c3f4f6945be2; >= 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e, < 2e16ae1464a4f435425c6f6ff1e293db850a624c; >= 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e, < a776d603d1e1bba2837295817b0a39394707b10d; >= 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e, < ce220b4cdf62f73db0c1940f968eb33b9899fdd0; >= 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e, < 6d1a984afc3ca477dab3e51ec806671d443ad524; >= 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e, < 6b7be3b9b857947e9c1338d4919d4ebd3b75e907; >= 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e, < 017b18addbe8dcace1a569a00d40ed1ba1e03f4c; >= 7ca0ff9ab3218ec443a7a9ad247e4650373ed41e, < b48820de8c1a596c5b99775524dfce73c6576c5d; 4260dc792fabfd20c8644fa9414b2ae48372365f; >= 2.6.31.2, < 2.6.32
LinuxLinux2.6.32

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98752?
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().
How severe is CVE-2026-98752?
Severity scoring for CVE-2026-98752 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-98752?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98752?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST