Menu

Star on GitHub · 3.2k

CVE-2026-64337

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…

Published Jul 25, 2026EPSS 0.16%

Overview

CVE-2026-64337 is a known-severity vulnerability. It was published on July 25, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-64337?

CVE-2026-64337 is a known-severity vulnerability. It was published on July 25, 2026.

How severe is CVE-2026-64337?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-64337?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64337?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64337 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.