Skip to main content
VulnerabilityPublished

CVE-2026-63904: Linux kernel · usb: usbtmc: check URB actual_length for interrupt-IN notifications

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 30 Oct 2026, 15:36 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

AI-suggested

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 Linux kernel updates that include this fix. No additional mitigation is indicated.

Description

A vulnerability in the Linux kernel 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 driver fails to verify that the URB actual_length is sufficient before accessing two-byte headers in notification messages, potentially leading to improper memory access.

References

Community reviews

Loading reviews…