Linux Kernel up to 7.2-rc2 mtu3 mtu3_gadget_queue memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.6$0-$5k4.65-

Summaryinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 7.2-rc2. This impacts the function mtu3_gadget_queue of the component mtu3. Performing a manipulation results in memory leak. This vulnerability is cataloged as CVE-2026-64337. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 7.2-rc2. This affects the function mtu3_gadget_queue of the component mtu3. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-64337 since 07/19/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/25/2026). The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4 or 7.2-rc3 eliminates this vulnerability. Applying the patch 3cee30f1138281a1d247bb053a1ad4f7c5b04e98/f3c4026524d3660c73ef2838b99776d37631e039/e8f739a3860d043dcc135371637e82f53132efe5/4183874b7925f4a98b400cf857bea26ee87da236/00c3fef4c2dc2c7cbd8281f8fda09d1913420f09/8c29d9cfab1c3cf0d0b7fcdf9255597be30aa3e1/835b0596d4c9bdef93f842d8f826978fb4956b74/0bddda5a11665c210339de76d27ebbd1a2e0b43c is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.0
VulDB Meta Temp Score: 8.6

VulDB Base Score: 9.0
VulDB Temp Score: 8.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.96/6.18.39/7.1.4/7.2-rc3
Patch: 3cee30f1138281a1d247bb053a1ad4f7c5b04e98/f3c4026524d3660c73ef2838b99776d37631e039/e8f739a3860d043dcc135371637e82f53132efe5/4183874b7925f4a98b400cf857bea26ee87da236/00c3fef4c2dc2c7cbd8281f8fda09d1913420f09/8c29d9cfab1c3cf0d0b7fcdf9255597be30aa3e1/835b0596d4c9bdef93f842d8f826978fb4956b74/0bddda5a11665c210339de76d27ebbd1a2e0b43c

Timelineinfo

07/19/2026 CVE reserved
07/25/2026 +6 days Advisory disclosed
07/25/2026 +0 days VulDB entry created
07/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64337 (🔒)
GCVE (CVE): GCVE-0-2026-64337
GCVE (VulDB): GCVE-100-383139

Entryinfo

Created: 07/25/2026 16:05
Changes: 07/25/2026 16:05 (59)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!