CVE-2026-64346

Description

A flaw was found in the Linux kernel's USB gadget driver. A race condition exists where the udc (USB Device Controller) memory, which manages USB gadgets, can be freed while still being accessed. This use-after-free vulnerability can be triggered by a local attacker, potentially through operations like mode-switching or configuration file system (configfs) interactions. Successful exploitation leads to a NULL pointer dereference, causing a system crash and resulting in a Denial of Service (DoS).

Statement

A use-after-free race exists in the USB gadget UDC core because the usb_udc object and the gadget device have decoupled lifetimes. usb_del_gadget() can free the UDC memory during mode switch work while gadget_match_driver() concurrently accesses the same object through the configfs UDC binding path, resulting in a kernel crash. The observed failure is a NULL-pointer dereference in strcmp after the freed memory is zeroed, but the underlying primitive is a race based UAF on a kernel management object. For the CVSS the PR:L is used in the paranoid score because gadget configfs or USB role control can be exposed to reduced capability local services on embedded systems, even though normal administration usually requires root or CAP_SYS_ADMIN. The issue is local and not directly network reachable.

Mitigation

Mitigation for this issue is either not available or the currently available options don't 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 HatNVDcve.org
Base Score4.77.8N/A
Attack VectorLocalLocalN/A
Attack ComplexityHighLowN/A
Privileges RequiredLowLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityNoneHighN/A
Integrity ImpactNoneHighN/A
Availability ImpactHighHighN/A

Vector

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.