CVE-2026-99297

Description

A flaw was found in the Linux kernel's em28xx USB media driver. When memory allocation fails during USB buffer initialization, an error-handling routine releases the allocated memory buffers twice. A local user or an attacker capable of connecting a crafted USB device could exploit this double-free flaw to cause memory corruption, leading to a system crash and Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate rather than Important because exploitation requires physical access to attach a specialized USB device or privileged access to emulate USB hardware in a virtual machine, alongside triggering a memory allocation error during device initialization. In standard enterprise Red Hat Enterprise Linux server environments, the em28xx media driver is not loaded by default or required for normal system operations. While triggering the double-free flaw can lead to kernel memory corruption and an immediate denial of service via a kernel crash, it does not directly enable arbitrary code execution or remote network exploitation.

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.2N/AN/A
Attack VectorPhysicalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability,Integrity

Technical Impact: DoS: Crash, Exit, or Restart

Integrity

Technical Impact: Modify Memory; Modify Application Data

Depending on the type of resource and the expected API behavior, this could lead to memory corruption, data corruption, or execution path corruption.

Frequently Asked Questions

Want to get errata notifications? Sign up here.