CVE-2026-64230

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

regulator: tps65219: fix irq_data.rdev not being assigned

Commit 64a6b577490c ("regulator: tps65219: Remove debugging helper function") removed the tps65219_get_rdev_by_name() helper along with the irq_data.rdev assignment that depended on it. This left irq_data.rdev uninitialized for all IRQs, causing undefined behavior when regulator_notifier_call_chain() is called from the IRQ handler:

Internal error: Oops: 0000000096000004 pc : regulator_notifier_call_chain lr : tps65219_regulator_irq_handler Call trace: regulator_notifier_call_chain tps65219_regulator_irq_handler handle_nested_irq regmap_irq_thread irq_thread_fn irq_thread kthread ret_from_fork

Instead of restoring a dedicated lookup array, restructure the probe function to combine regulator registration with IRQ registration in the same loop. This way the rdev returned by devm_regulator_register() is naturally available for assigning to irq_data.rdev without any auxiliary data structure.

Non-regulator IRQs (SENSOR, TIMEOUT) that don't correspond to any registered regulator are registered with rdev=NULL, and the IRQ handler is protected with a NULL check to avoid crashing.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 12, 2026

Advisory Details (3)

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

regulator: tps65219: fix irq_data.rdev not being assigned - kernel/git/stable/linux.git - Linux kernel stable tree

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

regulator: tps65219: fix irq_data.rdev not being assigned - kernel/git/stable/linux.git - Linux kernel stable tree

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

regulator: tps65219: fix irq_data.rdev not being assigned - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6827647fd2dcf4e7f355478a42e82f51e0b5344c

Vendor Advisories for CVE-2026-64230(1)

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

Patch Availability(3)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 21× in last 7d / 80× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:18 UTCEG score recompute
  3. 2026-08-30 00:18 UTCVendor advisory
  4. 2026-08-30 00:18 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 21:30 UTCEG score recompute
  7. 2026-08-27 21:30 UTCVendor advisory
  8. 2026-08-27 21:30 UTCGHSA enrichment
  9. 2026-08-26 19:52 UTCEG score recompute
  10. 2026-08-26 19:52 UTCVendor advisory
  11. 2026-08-26 19:52 UTCGHSA enrichment
  12. 2026-08-26 14:47 UTCEPSS rescore
  13. 2026-08-25 15:18 UTCEG score recompute
  14. 2026-08-25 15:18 UTCVendor advisory
  15. 2026-08-25 15:18 UTCGHSA enrichment
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-24 13:34 UTCEG score recompute
  18. 2026-08-24 13:34 UTCVendor advisory
  19. 2026-08-24 13:34 UTCGHSA enrichment
  20. 2026-08-23 11:57 UTCVendor advisory
  21. 2026-08-23 11:57 UTCGHSA enrichment
  22. 2026-08-22 10:20 UTCEG score recompute
  23. 2026-08-22 10:20 UTCVendor advisory
  24. 2026-08-22 10:20 UTCGHSA enrichment
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 73 more
  1. 2026-08-21 08:38 UTCEG score recompute
  2. 2026-08-21 08:38 UTCVendor advisory
  3. 2026-08-21 08:38 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 07:00 UTCEG score recompute
  6. 2026-08-20 07:00 UTCVendor advisory
  7. 2026-08-20 07:00 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 05:23 UTCEG score recompute
  10. 2026-08-19 05:23 UTCVendor advisory
  11. 2026-08-19 05:23 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 03:40 UTCEG score recompute
  14. 2026-08-18 03:40 UTCVendor advisory
  15. 2026-08-18 03:39 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 01:49 UTCEG score recompute
  18. 2026-08-17 01:49 UTCVendor advisory
  19. 2026-08-17 01:49 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 00:12 UTCEG score recompute
  22. 2026-08-16 00:12 UTCVendor advisory
  23. 2026-08-16 00:12 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 22:34 UTCEG score recompute
  26. 2026-08-14 22:34 UTCVendor advisory
  27. 2026-08-14 22:34 UTCGHSA enrichment
  28. 2026-08-13 22:00 UTCEPSS rescore
  29. 2026-08-13 20:56 UTCEG score recompute
  30. 2026-08-13 20:56 UTCVendor advisory
  31. 2026-08-13 20:56 UTCGHSA enrichment
  32. 2026-08-12 19:19 UTCEG score recompute 5.50
  33. 2026-08-12 19:19 UTCVendor advisory
  34. 2026-08-12 19:19 UTCGHSA enrichment
  35. 2026-08-12 19:18 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  36. 2026-08-12 13:51 UTCEPSS rescore
  37. 2026-08-11 16:47 UTCVendor advisory
  38. 2026-08-11 16:46 UTCGHSA enrichment
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-09 13:47 UTCEPSS rescore
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-08 16:24 UTCVendor advisory
  43. 2026-08-08 16:24 UTCGHSA enrichment
  44. 2026-08-06 13:47 UTCEPSS rescore
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-05 16:01 UTCVendor advisory
  48. 2026-08-05 16:01 UTCGHSA enrichment
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:39 UTCEPSS rescore
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 15:39 UTCVendor advisory
  53. 2026-08-02 15:39 UTCGHSA enrichment
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-30 16:28 UTCEPSS rescore
  57. 2026-07-30 15:16 UTCEG score recompute
  58. 2026-07-30 15:16 UTCGHSA enrichment
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-30 01:30 UTCEPSS rescore
  61. 2026-07-29 03:23 UTCEG score recompute
  62. 2026-07-29 03:23 UTCGHSA enrichment
  63. 2026-07-28 15:37 UTCEPSS rescore
  64. 2026-07-27 14:14 UTCEPSS rescore
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-26 02:59 UTCEG score recompute
  68. 2026-07-26 02:58 UTCGHSA enrichment
  69. 2026-07-25 14:18 UTCEPSS rescore
  70. 2026-07-25 14:18 UTCEPSS rescore
  71. 2026-07-24 16:31 UTCNVD update
  72. 2026-07-24 15:43 UTCEG score recompute
  73. 2026-07-24 15:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64230?
CVE-2026-64230 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: regulator: tps65219: fix irq_data.rdev not being assigned Commit 64a6b577490c ("regulator: tps65219: Remove debugging helper function") removed the tps65219getrdevbyname() helper along with the irq_data.rdev assignment that…
When was CVE-2026-64230 disclosed?
CVE-2026-64230 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64230 actively exploited?
CVE-2026-64230 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 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64230?
CVE-2026-64230 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64230?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64230, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64230

Explore →

Is Your Infrastructure Affected by CVE-2026-64230?

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