data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-98747 in the interactive tracker

CVE-2026-98747

serial: core: fix NULL pointer dereference in serial_core_unregister_port()

Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/tty. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-98747 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixievulnerable6.12.113-1No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication.
Debian 14forkyfixed7.2.10-1Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.2.10-1Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

port->port_dev is NULL when no port device is installed: it is cleared on teardown, and never set if registration failed before serial_core_port_device_add(). serial_core_unregister_port() passes it straight to serial_core_get_ctrl_dev(), which dereferences it: KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047] RIP: serial_core_unregister_port Call Trace: serial8250_unregister_port serial8250_remove unbind_store Return early when there is no port device, and read port->port_dev under port_mutex. Also clear port->port_dev on the serial_core_register_port() error path, where the port device has already been removed.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/tty/serial/serial_core.c

What this is
TTY LAYER AND SERIAL DRIVERSMAINTAINERS section matched on drivers/tty/ · linux-kernel@vger.kernel.org · Supported
Kernel module
serial_base

Check it on the machine

grep -w CONFIG_SERIAL_CORE /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w serial_base

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this code. Every release below compiles the affected file into the kernels it ships.

  • bookwormy
  • trixie, forky, sidb
y
built into the kernel image on every flavour - only a patch removes it
b
built in on some flavours, a module on others
Build switch
CONFIG_SERIAL_CORE

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-10-18 (today)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
not scored
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
drivers/tty

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.57.2.1054abbb862366
6.57.3499485a67fba

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98747, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.