CVE-2026-99779
Description
A flaw was found in the Linux kernel's 9P USB gadget transport driver. When a connected USB host resets or unconfigures the gadget interface, the driver fails to disable its endpoints and release allocated USB request objects. Upon subsequent device reconfiguration, new requests are allocated and overwrite previous references without freeing them. A connected host can exploit this issue to cause a permanent memory leak, potentially resulting in resource exhaustion and a Denial of Service (DoS).
Statement
This vulnerability is rated as Low severity for Red Hat because exploitation requires physical access from an attached USB host and depends on non-default USB gadget mode configuration. Standard enterprise server deployments function as USB hosts rather than peripheral gadget devices, leaving the vulnerable transport inactive in typical installations. Furthermore, triggering the condition requires repeated host-driven reconfiguration cycles and results solely in a gradual kernel memory leak, without granting code execution or data disclosure.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 2.4 | N/A | N/A |
| Attack Vector | Physical | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | None | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | Low | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (Other); DoS: Resource Consumption (Memory); DoS: Resource Consumption (CPU)
An attacker that can influence the allocation of resources that are not properly released could deplete the available resource pool and prevent all other processes from accessing the same type of resource. Frequently-affected resources include memory, CPU, disk space, power or battery, etc.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.