CVE-2026-63904

UnknownEPSS 0.21%

Last modified

CVE-2026-63904 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: usb: usbtmc: check URB actual_length for interrupt-IN notifications 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: usb: usbtmc: check URB actual_length for interrupt-IN notifications 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.

Metrics

EPSS Probability
0.21%

11.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= dbf3e7f654c0f06a932b8fcafac78de9d0b81d68, < e794bd67b3faf98af46f958897f6b91412c7d2a9; >= dbf3e7f654c0f06a932b8fcafac78de9d0b81d68, < e3eec3005de44e7f37d8d7724be636446516ab42; >= dbf3e7f654c0f06a932b8fcafac78de9d0b81d68, < ae87f505917e703ae3b487d9663d78826ff43608; >= dbf3e7f654c0f06a932b8fcafac78de9d0b81d68, < 5de7df75ef3a2756b25fe3d582a4a2970444fe5a; >= dbf3e7f654c0f06a932b8fcafac78de9d0b81d68, < 69020fa089f1bf0e1a10a15265f31b143a846409; >= dbf3e7f654c0f06a932b8fcafac78de9d0b81d68, < 75f6d3da2cc646983f41807ef98851569c12bca9; >= dbf3e7f654c0f06a932b8fcafac78de9d0b81d68, < f141b01eaa58ac7e323931d670318aa247bff087; >= dbf3e7f654c0f06a932b8fcafac78de9d0b81d68, < 52f2ad3f7e5eb3b5908e1d685d4342519dc9cfcd
LinuxLinux4.6

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-63904?
In the Linux kernel, the following vulnerability has been resolved: usb: usbtmc: check URB actual_length for interrupt-IN notifications 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.
How severe is CVE-2026-63904?
Severity scoring for CVE-2026-63904 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-63904?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-63904?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST