DMA mapping leak via failed request queueing
Published Jul 25, 2026 · Updated Jul 25, 2026
Resource leak in the Linux Kernel mtu3 USB gadget driver allows attackers to leave request DMA mappings active via unspecified vectors. mtu3_gadget_queue() maps a request before checking QMU GPD ring capacity, then returns EAGAIN without reaching mtu3_req_complete(), which normally unmaps it. The public record identifies no direct attacker-controlled vector and does not establish that repeated failures exhaust mappings or interrupt USB service.
Summary
What happened
Resource leak in the Linux Kernel mtu3 USB gadget driver allows attackers to leave request DMA mappings active via unspecified vectors. mtu3_gadget_queue() maps a request before checking QMU GPD ring capacity, then returns EAGAIN without reaching mtu3_req_complete(), which normally unmaps it. The public record identifies no direct attacker-controlled vector and does not establish that repeated failures exhaust mappings or interrupt USB service.
The record
- CVE
- CVE-2026-64337
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.10
- Affected versionversion=df2069acb00569a6299d6e11aa1865eeba463848 <00c3fef4c2dc2c7cbd8281f8fda09d1913420f09
- Affected versionversion=df2069acb00569a6299d6e11aa1865eeba463848 <0bddda5a11665c210339de76d27ebbd1a2e0b43c
- Affected versionversion=df2069acb00569a6299d6e11aa1865eeba463848 <3cee30f1138281a1d247bb053a1ad4f7c5b04e98
- Affected versionversion=df2069acb00569a6299d6e11aa1865eeba463848 <4183874b7925f4a98b400cf857bea26ee87da236
- Affected versionversion=df2069acb00569a6299d6e11aa1865eeba463848 <835b0596d4c9bdef93f842d8f826978fb4956b74
- Affected versionversion=df2069acb00569a6299d6e11aa1865eeba463848 <8c29d9cfab1c3cf0d0b7fcdf9255597be30aa3e1
- Affected versionversion=df2069acb00569a6299d6e11aa1865eeba463848 <e8f739a3860d043dcc135371637e82f53132efe5
- Affected versionversion=df2069acb00569a6299d6e11aa1865eeba463848 <f3c4026524d3660c73ef2838b99776d37631e039
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo