CVE-2026-99554
Description
A flaw was found in the Linux kernel's Pegasus USB Ethernet driver. This vulnerability can result in a Denial of Service (DoS) by causing a system crash when an attacker connects a malicious Universal Serial Bus (USB) device. By transmitting a stream of oversized network packets, the device causes the driver to advance its internal receive buffer past allocated memory, triggering an out-of-bounds memory write.
Statement
This vulnerability is rated as having a Moderate impact because exploitation requires physical access to connect a malicious USB device or administrative access to attach an emulated device to a virtualized guest. In typical Red Hat Enterprise Linux installations, the Pegasus USB Ethernet driver is not loaded unless matching hardware is connected. Successful exploitation leads to kernel memory corruption and a system crash (denial of service), but cannot be triggered remotely across a network.
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 | 4.6 | N/A | N/A |
| Attack Vector | Physical | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | None | 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:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.