Skip to content
Fencer Intel
no cvss —

CVE-2026-98753 json

tty: tty_port: restore TTY_IO_ERROR on activation failure

published 24d ago modified 12d ago also EUVD-2026-103838

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: tty_port: restore TTY_IO_ERROR on activation failure

Make sure to restore the TTY_IO_ERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down.

This specifically avoids issues like kernel panic due to unclocked accesses or NULL-pointer dereferences when accessing powered down or deregistered ports when a TTY ioctl races with hangup and open.

Note that the flag is set again in tty_port_close() but not restoring it on activation failure leaves a window where drivers fail to handle the ioctl-hangup race.

Patch / fix

  • Linux Linux 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-98753

  • 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-98753

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-109020

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

Is CVE-2026-98753 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 Fencer

Vendor 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-98753 updated cvss 4.7

kernel: tty: tty_port: restore TTY_IO_ERROR on activation failure

  • 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-9
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    not 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

Sources

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.