Impact
The Chrome OS cros_ec driver assigns a pointer to its platform device before confirming that initialization has fully succeeded; if the probe fails, the driver data remains registered, allowing a sub‑driver such as cros_ec_typec to later dereference the stale pointer, which produces a use‑after‑free that can corrupt kernel memory or trigger a crash.
Affected Systems
Any Linux kernel build that includes the cros_ec and related cros_ec_typec modules, which are commonly loaded in Chrome OS hardware, is affected; systems that load these modules during boot or from a module load before the patch will be vulnerable.
Risk and Exploitability
The CVSS score of 7 indicates a medium‑high severity, while the EPSS score of less than 1% signifies a very low likelihood of exploitation; the vulnerability is not listed in CISA KEV, and based on the description it is inferred that exploitation would require local access to trigger a probe failure or manipulate the device initialization sequence, making remote exploitation unlikely.
OpenCVE Enrichment
Debian DLA
Ubuntu USN