CVE-2026-80659
Description
A flaw was found in the Linux kernel's vub300 driver. When the vub300_cmndwork_thread() function holds a command mutex and a command response times out, the device reset path attempts to re-acquire the same mutex recursively. This recursive locking can lead to a deadlock, causing a Denial of Service (DoS) condition for the system.
Statement
A low impact flaw was found in the Linux kernel vub300 USB MMC host driver, affecting Red Hat Enterprise Linux 7 through 10 and Red Hat In-Vehicle OS. When a command response times out while vub300_cmndwork_thread() holds cmd_mutex, __vub300_command_response() kills the command URBs and synchronously resets the USB device through usb_reset_device(). That reset path re-enters the driver via vub300_pre_reset(), which attempts to acquire cmd_mutex again while it is still held by the same task, deadlocking the command worker and leaving the MMC request path hung, resulting in a local denial of service. Confidentiality and integrity are not affected and there is no evidence of memory corruption or privilege escalation. Triggering the flaw requires a VUB300 USB MMC device to be present and a command response timeout to occur, so systems without such hardware are not exposed to this code path. Red Hat Enterprise Linux 6 is not affected because the vulnerable code is not present. For the affected streams the fix is currently deferred; the residual risk is limited to a hung kernel workqueue thread causing local denial of service on systems using this specific USB MMC hardware. Although the CVSS:3.1 base score is 5.5 (Moderate), Red Hat rates the impact of this flaw as low because it is not network reachable, requires this specific USB hardware, and only causes local denial of service.
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 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | 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 | High | N/A | N/A |
Vector
Red Hat: 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 (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart
Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.