In the Linux kernel, the following vulnerability has been resolved: usb: usbtmc: check URB actual_length for interrupt-IN notifications USBTMC… (CVE-2026-63904)
A vulnerability in the Linux kernel's USBTMC driver allows out-of-bounds reads or use of stale data due to missing checks on the actual length of interrupt-IN notification data. The issue arises when the driver accesses notification headers without verifying that the data buffer contains enough bytes, potentially leading to memory safety issues. The vulnerability has been resolved by adding checks on the actual_length field before processing the data.
AI Analysis
Technical Summary
The Linux kernel USBTMC driver handles optional interrupt endpoints for notification messages, which include two-byte headers indicating payload format. Prior to the fix, the driver did not verify that the URB actual_length was sufficient to contain these headers before accessing the data buffer. This could cause out-of-bounds reads or consumption of stale leftover data from previous notifications. The patch adds a check to ensure the actual_length is adequate; if not, the URB is resubmitted to the interrupt endpoint to prevent unsafe memory access.
Potential Impact
This vulnerability can lead to out-of-bounds memory reads or use of stale data within the USBTMC driver in the Linux kernel. Such memory safety issues may cause kernel instability or potentially expose sensitive data. However, no known exploits in the wild have been reported, and the impact is limited to systems using USBTMC devices with interrupt-IN notifications.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to check the URB actual_length before accessing interrupt-IN notification headers. Users should apply the official kernel updates that include this patch to remediate the vulnerability. Since this is a kernel-level issue, updating the kernel to a version containing the fix is the recommended mitigation.
In the Linux kernel, the following vulnerability has been resolved: usb: usbtmc: check URB actual_length for interrupt-IN notifications USBTMC… (CVE-2026-63904)
Description
A vulnerability in the Linux kernel's USBTMC driver allows out-of-bounds reads or use of stale data due to missing checks on the actual length of interrupt-IN notification data. The issue arises when the driver accesses notification headers without verifying that the data buffer contains enough bytes, potentially leading to memory safety issues. The vulnerability has been resolved by adding checks on the actual_length field before processing the data.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel USBTMC driver handles optional interrupt endpoints for notification messages, which include two-byte headers indicating payload format. Prior to the fix, the driver did not verify that the URB actual_length was sufficient to contain these headers before accessing the data buffer. This could cause out-of-bounds reads or consumption of stale leftover data from previous notifications. The patch adds a check to ensure the actual_length is adequate; if not, the URB is resubmitted to the interrupt endpoint to prevent unsafe memory access.
Potential Impact
This vulnerability can lead to out-of-bounds memory reads or use of stale data within the USBTMC driver in the Linux kernel. Such memory safety issues may cause kernel instability or potentially expose sensitive data. However, no known exploits in the wild have been reported, and the impact is limited to systems using USBTMC devices with interrupt-IN notifications.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to check the URB actual_length before accessing interrupt-IN notification headers. Users should apply the official kernel updates that include this patch to remediate the vulnerability. Since this is a kernel-level issue, updating the kernel to a version containing the fix is the recommended mitigation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-7gx5-8c2m-vqr5
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63904"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ab2a4a8d598912f911
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 07/19/2026, 20:09:46 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.