CVE-2026-99581
Description
A flaw was found in the Linux kernel's ChromeOS platform driver (cros_usbpd_notify). The driver incorrectly assumes parent device data represents a Chrome Embedded Controller (EC) structure without validating the device hierarchy. During USB-C Power Delivery (PD) events, such as plugging or unplugging a charger, this invalid data access can trigger a kernel crash, resulting in a denial of service (DoS) and system hang.
Statement
This vulnerability is rated as Moderate severity for Red Hat enterprise products because exploitation requires physical access to connect or disconnect power hardware on specialized ChromeOS platforms, resulting solely in a local denial of service. The affected ChromeOS platform driver is not utilized in standard enterprise server environments or standard bare-metal hardware. Furthermore, virtualized enterprise deployments do not expose this platform interface, preventing remote or software-only 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 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)
Other
Technical Impact: Varies by Context
When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties.
Availability,Integrity,Confidentiality
Technical Impact: Read Memory; Modify Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart
If a memory buffer is accessed using an incompatible type, and the allocated buffer is smaller than the type that the code is attempting to access, then an attacker could read or write memory outside the bounds of the buffer, leading to a crash or possibly code execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.