Skip to main content

Linux Kernel CVE-2026-72395

| EUVDEUVD-2026-59294 HIGH
2026-08-15 Linux GHSA-w4gm-vhrh-5h95
7.1
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.1 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
vuln.today AI
7.1 HIGH

Local vector confirmed; PR:L because triggering simultaneous hardware faults requires some system access; no confidentiality impact from event-handling logic bypass.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
4.2 MEDIUM
AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 09:02 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.1 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 05:56 cve.org
HIGH 7.1
CVE Published
Aug 15, 2026 - 05:56 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

hwmon: (pmbus) Fix passing events to regulator core

Sashiko reports:

Commit 754bd2b4a084 ("hwmon: (pmbus/core) Protect regulator operations with mutex") introduced a worker to batch regulator events over time using atomic_or(). The delayed worker then passes the combined bitmask unmodified to regulator_notifier_call_chain().

The core regulator subsystem's regulator_handle_critical() function evaluates the event parameter using a strict switch statement. If multiple distinct faults occur before the worker runs (e.g., REGULATOR_EVENT_UNDER_VOLTAGE | REGULATOR_EVENT_OVER_CURRENT), the combined bitmask fails to match any case. This leaves the reason as NULL and completely bypasses the critical hw_protection_trigger().

Fix the problem by passing events bit by bit to the regulator event handler.

AnalysisAI

Hardware protection bypass in the Linux kernel's PMBus hwmon driver silently discards concurrent regulator fault events, preventing hw_protection_trigger() from firing when multiple power faults coincide. Systems running affected kernel versions (6.6.143-6.6.145, 6.12.92-6.12.97, 6.18.21-6.18.40, 6.19.11-6.20, 7.0-7.1.4) with PMBus-managed power rails may fail to respond to simultaneous under-voltage and over-current events, leaving hardware operating without critical protection. No public exploit has been identified; EPSS of 0.22% (13th percentile) and absence from CISA KEV confirm this is not actively exploited.

Technical ContextAI

The flaw resides in the Linux kernel's PMBus (Power Management Bus) hardware monitor driver, introduced by commit 754bd2b4a084 ('hwmon: (pmbus/core) Protect regulator operations with mutex'). That commit added a delayed worker that uses atomic_or() to batch concurrent regulator events before dispatch. The defect emerges when two or more distinct hardware fault conditions - for example REGULATOR_EVENT_UNDER_VOLTAGE and REGULATOR_EVENT_OVER_CURRENT - are OR'd together before the worker fires, producing a combined bitmask. The regulator core's regulator_handle_critical() function evaluates the event parameter via a strict switch statement that only matches individual, single-bit event values; the combined bitmask matches no case, the 'reason' variable remains NULL, and hw_protection_trigger() is never called. No CWE is formally assigned; the root cause most closely resembles CWE-697 (Incorrect Comparison) combined with CWE-691 (Insufficient Control Flow Management). CPE cpe:2.3:a:linux:linux:* confirms applicability across Linux kernel builds where the pmbus driver is present and PMBus hardware is attached.

RemediationAI

Upgrade to a patched stable kernel release appropriate for the active series: 6.6.145, 6.12.97, 6.18.40, or 7.1.5. Mainline users should target 7.2-rc2 or later. Individual upstream fix commits are available at https://git.kernel.org/stable/c/2106bf4056858fcce3624e0c51f6fee4d41d3f2f (6.12 series), https://git.kernel.org/stable/c/48fe43666950efefb7ac5fbdc012c1b3604096bf (6.6 series), https://git.kernel.org/stable/c/489291b6b56978cc50d34e8e13f9636ea296ba8a, https://git.kernel.org/stable/c/b0ff6b6ae9c5183ef701ece7016698bde5a5bfba, and https://git.kernel.org/stable/c/9ef7dacd44216bf5ea05c8aef49eba4d145f4047 for remaining branches. If immediate patching is not feasible, unloading the pmbus kernel module (rmmod pmbus) removes the vulnerable code path but will disable all PMBus-based hardware monitoring and any regulator control, which may be operationally unacceptable on servers relying on PMBus for voltage/thermal management. No network-level mitigations are applicable given the strictly local attack vector.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-72395 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy