CVE-2026-98752 json
tty: port: fix tty_port_tty_vhangup() race
published 24d ago modified 12d ago also EUVD-2026-103837
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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().
Patch / fix
- Linux Linux 2.6.32, 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.10-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98752
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-43.43
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1017.18
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1017.19
- linux-gke Ubuntu 24.04 LTS 6.8.0-1068.77
- linux-gke Ubuntu 26.04 LTS 7.0.0-1010.11
ubuntu advisories UBUNTU-CVE-2026-98752
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-109184
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/a78910f6d78cc1415cbc9b4fb621c3f4f6945be2 commit
- git.kernel.org/stable/c/2e16ae1464a4f435425c6f6ff1e293db850a624c commit
- git.kernel.org/stable/c/a776d603d1e1bba2837295817b0a39394707b10d commit
- git.kernel.org/stable/c/ce220b4cdf62f73db0c1940f968eb33b9899fdd0 commit
- git.kernel.org/stable/c/6d1a984afc3ca477dab3e51ec806671d443ad524 commit
- git.kernel.org/stable/c/6b7be3b9b857947e9c1338d4919d4ebd3b75e907 commit
- git.kernel.org/stable/c/017b18addbe8dcace1a569a00d40ed1ba1e03f4c commit
- git.kernel.org/stable/c/b48820de8c1a596c5b99775524dfce73c6576c5d commit
Is CVE-2026-98752 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98752 updated cvss 4.7
kernel: tty: port: fix tty_port_tty_vhangup() race
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/a78910f6d78cc1415cbc9b4fb621c3f4f6945be2
- git.kernel.org /stable/c/2e16ae1464a4f435425c6f6ff1e293db850a624c
- git.kernel.org /stable/c/a776d603d1e1bba2837295817b0a39394707b10d
- git.kernel.org /stable/c/ce220b4cdf62f73db0c1940f968eb33b9899fdd0
- git.kernel.org /stable/c/6d1a984afc3ca477dab3e51ec806671d443ad524
- git.kernel.org /stable/c/6b7be3b9b857947e9c1338d4919d4ebd3b75e907
- git.kernel.org /stable/c/017b18addbe8dcace1a569a00d40ed1ba1e03f4c
- git.kernel.org /stable/c/b48820de8c1a596c5b99775524dfce73c6576c5d
Sources
- CVE List CVE-2026-98752
- NVD CVE-2026-98752
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.