Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63904, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (22 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 – < e794bd67b3faf98af46f958897f6b91412c7d2a9
    • affected dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 – < e3eec3005de44e7f37d8d7724be636446516ab42
    • affected dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 – < ae87f505917e703ae3b487d9663d78826ff43608
    • affected dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 – < 5de7df75ef3a2756b25fe3d582a4a2970444fe5a
    • affected dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 – < 69020fa089f1bf0e1a10a15265f31b143a846409
    • affected dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 – < 75f6d3da2cc646983f41807ef98851569c12bca9
    • affected dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 – < f141b01eaa58ac7e323931d670318aa247bff087
    • affected dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 – < 52f2ad3f7e5eb3b5908e1d685d4342519dc9cfcd
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63904 badge
[![CVE-2026-63904](https://cveledger.app/badge/CVE-2026-63904.svg)](https://cveledger.app/cve/CVE-2026-63904)

Record last updated .