CVE-2026-99308

Description

A flaw was found in the Linux kernel's USB eXtensible Host Controller Interface (xHCI) driver. An attacker with physical access could connect a malicious USB device configured with out-of-specification endpoint sizes to trigger a buffer overflow during data transfer operations. This issue occurs because the driver allocates a smaller bounce buffer than indicated by the device descriptor, leading to memory corruption. A successful exploit could result in a system crash, causing a Denial of Service (DoS), or potentially allow arbitrary code execution.

Statement

This vulnerability is rated as Moderate severity because exploitation requires physical access to attach a malicious or non-compliant USB peripheral, or access to pass through an emulated device in virtualized environments. While an out-of-spec endpoint descriptor can trigger memory corruption within the kernel host controller subsystem resulting in a crash or privilege escalation, the prerequisite of local hardware or hypervisor access significantly limits exposure for standard server deployments.

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 Score6.8N/AN/A
Attack VectorPhysicalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.