Bug 2502458 (CVE-2026-63904) - CVE-2026-63904 kernel: usb: usbtmc: check URB actual_length for interrupt-IN notifications
Summary: CVE-2026-63904 kernel: usb: usbtmc: check URB actual_length for interrupt-IN ...
Keywords:
Status: NEW
Alias: CVE-2026-63904
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-19 16:09 UTC by OSIDB Bzimport
Modified: 2026-07-21 11:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-19 16:09:16 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-07-21 11:41:59 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026071944-CVE-2026-63904-e989@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.