CVE-2026-72395

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

hwmon: (pmbus) Fix passing events to regulator core - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b0ff6b6ae9c5183ef701ece7016698bde5a5bfba
generic

hwmon: (pmbus) Fix passing events to regulator core - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ef7dacd44216bf5ea05c8aef49eba4d145f4047
generic

hwmon: (pmbus) Fix passing events to regulator core - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48fe43666950efefb7ac5fbdc012c1b3604096bf
generic

hwmon: (pmbus) Fix passing events to regulator core - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/489291b6b56978cc50d34e8e13f9636ea296ba8a
generic

hwmon: (pmbus) Fix passing events to regulator core - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2106bf4056858fcce3624e0c51f6fee4d41d3f2f

Vendor Advisories for CVE-2026-72395(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 29× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 06:59 UTCEG score recompute
  2. 2026-08-21 06:59 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 18:59 UTCGHSA enrichment
  5. 2026-08-20 06:59 UTCGHSA enrichment
  6. 2026-08-19 19:00 UTCEG score recompute
  7. 2026-08-19 19:00 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 06:59 UTCGHSA enrichment
  10. 2026-08-18 18:59 UTCGHSA enrichment
  11. 2026-08-18 06:59 UTCGHSA enrichment
  12. 2026-08-17 18:59 UTCEG score recompute
  13. 2026-08-17 18:59 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:29 UTCEG score recompute
  16. 2026-08-17 06:29 UTCGHSA enrichment
  17. 2026-08-17 05:57 UTCEG score recompute▲ 7.10
  18. 2026-08-17 05:57 UTCGHSA enrichment
  19. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  20. 2026-08-17 05:29 UTCEG score recompute
  21. 2026-08-17 05:29 UTCGHSA enrichment
  22. 2026-08-17 05:24 UTCMITRE cvelistV5
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 4 more
  1. 2026-08-15 06:34 UTCGHSA enrichment
  2. 2026-08-15 06:23 UTCNVD update
  3. 2026-08-15 06:05 UTCEG score recompute
  4. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72395?
CVE-2026-72395 is a high vulnerability published on August 15, 2026. 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…
When was CVE-2026-72395 disclosed?
CVE-2026-72395 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72395 actively exploited?
CVE-2026-72395 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
What is the CVSS score of CVE-2026-72395?
CVE-2026-72395 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-72395?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72395, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72395

Explore →

Is Your Infrastructure Affected by CVE-2026-72395?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs