CVE-2026-63904

What the bug is

USBTMC devices can use an optional interrupt endpoint for notification messages. These typically contain two-byte headers indicating the payload format, but the driver does not check if these headers are present before accessing the data buffers. In cases where the URB actual_length is not enough to fit these headers, the driver will either cause an out-of-bounds read, or consume stale leftover data from a previous notification. Fix by checking if actual_data contains enough bytes for the headers, otherwise resubmit URB to the interrupt endpoint.

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/usb/class/usbtmc.c

What this is

USB SUBSYSTEMMAINTAINERS section matched on drivers/usb/ · linux-usb@vger.kernel.org · Supported

Kernel module

usbtmc

Check it on the machine

grep -wE 'CONFIG_OF|CONFIG_PCI|CONFIG_USB|CONFIG_USB_ACM|CONFIG_USB_GADGET|CONFIG_USB_PHY|CONFIG_USB_PRINTER|CONFIG_USB_SUPPORT|CONFIG_USB_TMC|CONFIG_USB_WDM' /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 usbtmc

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, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

• bookwormMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-arm64, i386/686, i386/686-pae, i386/rt/686-pae, ppc64el/powerpc64le
• trixieMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/cloud-arm64, armel/rpi, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
• forky, sidMnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/cloud-arm64, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x

M

a module where it is built at all; some flavours do not build it

Build switches

CONFIG_OF, CONFIG_PCI, CONFIG_USB, CONFIG_USB_ACM, CONFIG_USB_GADGET, CONFIG_USB_PHY, CONFIG_USB_PRINTER, CONFIG_USB_SUPPORT, CONFIG_USB_TMC, CONFIG_USB_WDM

Reads as

all on means the file is compiled; any one off means it is not.

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-07-19 (3 months ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.23%, higher than 12.3% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/usb

Upstream fixes

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

Introduced	Fixed in	Commit
4.6	5.10.259	e794bd67b3fa
4.6	5.15.210	e3eec3005de4
4.6	6.1.176	ae87f505917e
4.6	6.6.143	5de7df75ef3a
4.6	6.12.93	69020fa089f1
4.6	6.18.35	75f6d3da2cc6
4.6	7.0.12	f141b01eaa58
4.6	7.1	52f2ad3f7e5e