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

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

CVE-2026-23472

serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN

EPSS 0.1%

Published 2026-04-03 (7 months ago) by the Linux kernel CNA. Subsystem drivers/tty. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-23472 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 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
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 14forkyfixed6.19.10-1Update the kernel and reboot. Fixed in 6.19.10-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.19.10-1Update the kernel and reboot. Fixed in 6.19.10-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

uart_write_room() and uart_write() behave inconsistently when xmit_buf is NULL (which happens for PORT_UNKNOWN ports that were never properly initialized): - uart_write_room() returns kfifo_avail() which can be > 0 - uart_write() checks xmit_buf and returns 0 if NULL This inconsistency causes an infinite loop in drivers that rely on tty_write_room() to determine if they can write: while (tty_write_room(tty) > 0) { written = tty->ops->write(...); // written is always 0, loop never exits } For example, caif_serial's handle_tx() enters an infinite loop when used with PORT_UNKNOWN serial ports, causing system hangs. Fix by making uart_write_room() also check xmit_buf and return 0 if it's NULL, consistent with uart_write(). Reproducer: https://gist.github.com/mrpre/d9a694cc0e19828ee3bc3b37983fde13

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-04-03 (7 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.12%, higher than 1.8% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/tty

Upstream fixes

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

IntroducedFixed inCommit
2.6.126.18.20efe85a557186
2.6.126.19.10bc70f2b36cf4
2.6.127.0455ce986fa35

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-23472, 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.