Cyber Resilience

CVE-2025-22095

Linux Kernel 6.0 – 6.1.134

Published
16 April 2025
Modified
14 July 2026
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0019 9th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-22095 is a medium-severity an unspecified weakness vulnerability in Linux Linux Kernel. Its CVSS base score is 5.5 (Medium).

Operationally, ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-11 (Error Handling) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: PCI: brcmstb: Fix error path after a call to regulator_bulk_get() If the regulator_bulk_get() returns an error and no regulators are created, we need to set their number to zero. If…

more

we don't do this and the PCIe link up fails, a call to the regulator_bulk_free() will result in a kernel panic. While at it, print the error value, as we cannot return an error upwards as the kernel will WARN() on an error from add_bus(). [kwilczynski: commit log, use comma in the message to match style with other similar messages]

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-1582Same product: Linux Linux Kernel
CVE-2023-52792Same product: Linux Linux Kernel
CVE-2024-35859Same product: Linux Linux Kernel
CVE-2023-52825Same product: Linux Linux Kernel
CVE-2024-56554Same product: Linux Linux Kernel
CVE-2024-56712Same product: Linux Linux Kernel
CVE-2024-43825Same product: Linux Linux Kernel
CVE-2023-52529Same product: Linux Linux Kernel
CVE-2024-42259Same product: Linux Linux Kernel
CVE-2024-26828Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
6.0 — 6.1.134 · 6.2 — 6.6.87 · 6.7 — 6.12.23

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires the system to identify and handle error conditions (regulator_bulk_get failure path) without causing a kernel panic on subsequent regulator_bulk_free.

prevent

Mandates fail-safe procedures so that an error in the PCIe regulator initialization path results in a safe state rather than a crash.

prevent

Requires timely application of the kernel patch that corrects the missing zeroing of regulator count after regulator_bulk_get failure.

References