CVE-2026-63904: usb: usbtmc: check URB actual_length for interrupt-IN notifications
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 52f2ad3f7e5eb3b5908e1d685d4342519dc9cfcd, 5de7df75ef3a2756b25fe3d582a4a2970444fe5a, 69020fa089f1bf0e1a10a15265f31b143a846409.
Low priority for now. Upgrade to Linux Linux 52f2ad3f7e5eb3b5908e1d685d4342519dc9cfcd, 5de7df75ef3a2756b25fe3d582a4a2970444fe5a, 69020fa089f1bf0e1a10a15265f31b143a846409 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 19, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-125
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.6affected
- dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 and later · before e794bd67b3faf98af46f958897f6b91412c7d2a9affected · git
- dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 and later · before e3eec3005de44e7f37d8d7724be636446516ab42affected · git
- dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 and later · before ae87f505917e703ae3b487d9663d78826ff43608affected · git
- dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 and later · before 5de7df75ef3a2756b25fe3d582a4a2970444fe5aaffected · git
- dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 and later · before 69020fa089f1bf0e1a10a15265f31b143a846409affected · git
- dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 and later · before 75f6d3da2cc646983f41807ef98851569c12bca9affected · git
- dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 and later · before f141b01eaa58ac7e323931d670318aa247bff087affected · git
- dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 and later · before 52f2ad3f7e5eb3b5908e1d685d4342519dc9cfcdaffected · git
- before 4.6not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.6 and later · before 5.10.259
- linux linux kernel5.11 and later · before 5.15.210
- linux linux kernel5.16 and later · before 6.1.176
- linux linux kernel6.2 and later · before 6.6.143
- linux linux kernel6.7 and later · before 6.12.93
- linux linux kernel6.13 and later · before 6.18.35
- linux linux kernel6.19 and later · before 7.0.12
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63902Jul 19, 2026 · USB: serial: cypress_m8: validate interrupt packet headers28Monitor
- ← EarlierCVE-2026-63903Jul 19, 2026 · USB: serial: belkin_sa: validate interrupt status length28Monitor
- Later →CVE-2026-63905Jul 19, 2026 · usbip: vudc: Fix use after free bug in vudc_remove due to race condition31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 52f2ad3f7e5eb3b5908e1d685d4342519dc9cfcd | Vendor (CNA) |
| Linux Linux | 5de7df75ef3a2756b25fe3d582a4a2970444fe5a | Vendor (CNA) |
| Linux Linux | 69020fa089f1bf0e1a10a15265f31b143a846409 | Vendor (CNA) |
| Linux Linux | 75f6d3da2cc646983f41807ef98851569c12bca9 | Vendor (CNA) |
| Linux Linux | ae87f505917e703ae3b487d9663d78826ff43608 | Vendor (CNA) |
| Linux Linux | e3eec3005de44e7f37d8d7724be636446516ab42 | Vendor (CNA) |
| Linux Linux | e794bd67b3faf98af46f958897f6b91412c7d2a9 | Vendor (CNA) |
| Linux Linux | f141b01eaa58ac7e323931d670318aa247bff087 | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- CVSS— → 7.1
- Severity— → high
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5de7df75ef3a2756b25fe3d582a4a2970444fe5a
- git.kernel.org/stable/c/69020fa089f1bf0e1a10a15265f31b143a846409
- git.kernel.org/stable/c/75f6d3da2cc646983f41807ef98851569c12bca9
- git.kernel.org/stable/c/ae87f505917e703ae3b487d9663d78826ff43608
- git.kernel.org/stable/c/e3eec3005de44e7f37d8d7724be636446516ab42
- git.kernel.org/stable/c/e794bd67b3faf98af46f958897f6b91412c7d2a9
- git.kernel.org/stable/c/f141b01eaa58ac7e323931d670318aa247bff087
Vendor advisories and official records. Exploit/PoC links are deliberately left out.