CVE-2026-31672
Description
A flaw was found in the Linux kernel's rt2x00usb component, which handles Wi-Fi USB devices. This issue stems from improper management of system memory allocated for USB devices. When a Wi-Fi USB device driver is unloaded without the device being physically disconnected, the system may fail to release the allocated memory, leading to a memory leak. Over time, this could exhaust system resources, potentially causing a Denial of Service (DoS) where the system becomes unresponsive or crashes.
Statement
A moderate-severity flaw was found in the Linux kernel's rt2x00usb driver, which handles Wi-Fi USB devices. The USB anchor used by the driver was allocated as a device-managed resource tied to the parent USB device rather than to the USB interface the driver binds to. As a result, when the driver is unbound from the interface without the device being physically disconnected (for example, on probe deferral or configuration changes), the allocated memory is not released, producing a kernel memory leak. A local attacker with the privileges needed to unbind and rebind the driver could repeat this cycle to gradually exhaust kernel memory, ultimately causing a denial of service. Only availability is affected; there is no impact on confidentiality or integrity. Red Hat rated this flaw Moderate severity with CVSS 3.1 score 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), consistent with the upstream NIST assessment.
The vulnerable code is present in the kernel and kernel-rt packages of Red Hat Enterprise Linux 8, 9, and 10, and in the kernel package of Red Hat In-Vehicle OS 2, which are therefore affected. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable code is not present in those releases. For most affected streams the fix is deferred to a future maintenance update; the residual risk of this deferral is considered low because exploitation requires local privileged access to repeatedly unbind the driver, memory accumulates only gradually across such cycles, and no confidentiality or integrity impact exists.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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 | 5.5 | 5.5 | N/A |
| Attack Vector | Local | Local | N/A |
| Attack Complexity | Low | Low | N/A |
| Privileges Required | Low | Low | N/A |
| User Interaction | None | None | N/A |
| Scope | Unchanged | Unchanged | N/A |
| Confidentiality | None | None | N/A |
| Integrity Impact | None | None | N/A |
| Availability Impact | High | High | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
An adversary that can cause a resource counter to become inaccurate may be able to create situations where resources are not accounted for and not released, thus causing resources to become scarce for future needs.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An adversary that can cause a resource counter to become inaccurate may be able to force an error that causes the product to crash or exit out of its current operation.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
