CVE-2026-99778

Description

A flaw was found in the Linux kernel's 9P USB gadget transport driver. When disabling a 9P USB connection, the driver improperly releases the request structure without freeing its associated data buffer. A local user could repeatedly trigger this cleanup routine to continuously leak kernel memory, potentially exhausting system resources and causing a Denial of Service (DoS).

Statement

This vulnerability is rated with a Low severity because it is limited to a local denial of service via memory exhaustion and depends on an uncommonly used kernel feature. The 9P USB gadget transport is not enabled or utilized in typical Red Hat Enterprise Linux deployments, as gadget mode requires specific USB device controller hardware or emulation. Exploitation requires repeated teardowns of 9P gadget connections to consume host memory, with no risk to data integrity or confidentiality.

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 HatNVDcve.org
Base Score3.3N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactLowN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/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

Want to get errata notifications? Sign up here.