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-64337

usb: mtu3: unmap request DMA on queue failure

Description

In the Linux kernel, the following vulnerability has been resolved: usb: mtu3: unmap request DMA on queue failure mtu3_gadget_queue() maps the request before checking whether the QMU GPD ring can accept another transfer. the request is returned with -EAGAIN before it is linked on the endpoint request list if mtu3_prepare_transfer() fails. Normal completion and dequeue paths unmap requests from mtu3_req_complete(), but this error path never reaches that helper, so the DMA mapping is left active. Unmap the request before returning from the failed queue path.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 23 days later

    Record updated

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-64337, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected df2069acb00569a6299d6e11aa1865eeba463848 – < 3cee30f1138281a1d247bb053a1ad4f7c5b04e98
    • affected df2069acb00569a6299d6e11aa1865eeba463848 – < f3c4026524d3660c73ef2838b99776d37631e039
    • affected df2069acb00569a6299d6e11aa1865eeba463848 – < e8f739a3860d043dcc135371637e82f53132efe5
    • affected df2069acb00569a6299d6e11aa1865eeba463848 – < 4183874b7925f4a98b400cf857bea26ee87da236
    • affected df2069acb00569a6299d6e11aa1865eeba463848 – < 00c3fef4c2dc2c7cbd8281f8fda09d1913420f09
    • affected df2069acb00569a6299d6e11aa1865eeba463848 – < 8c29d9cfab1c3cf0d0b7fcdf9255597be30aa3e1
    • affected df2069acb00569a6299d6e11aa1865eeba463848 – < 835b0596d4c9bdef93f842d8f826978fb4956b74
    • affected df2069acb00569a6299d6e11aa1865eeba463848 – < 0bddda5a11665c210339de76d27ebbd1a2e0b43c
  • Linux · Linux

    • affected 4.10
    • unaffected < 4.10
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .