CVE-2026-64213

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:

hwmon: (lm90) Add lock protection to lm90_alert

Sashiko reports:

lm90_alert() executes in the smbus alert context and calls lm90_update_confreg() to disable the hardware alert line, without acquiring hwmon_lock.

Concurrently, sysfs write operations (such as lm90_write_convrate) hold the hwmon_lock, temporarily modify data->config, and then restore it.

If an alert interrupt occurs concurrently with a sysfs write, the sysfs path will overwrite the alert handler's modifications to data->config and the hardware register.

This unintentionally re-enables the hardware alert line while the alarm is still active, causing an interrupt storm.

Add the missing lock to lm90_alert() to solve the problem.

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 11, 2026

Advisory Details (3)

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

hwmon: (lm90) Add lock protection to lm90_alert - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (lm90) Add lock protection to lm90_alert - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (lm90) Add lock protection to lm90_alert - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/873e919e3101063a7a75989510ccfc125a4391cf

Vendor Advisories for CVE-2026-64213(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

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

Frequently asked(5)

What is CVE-2026-64213?
CVE-2026-64213 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: hwmon: (lm90) Add lock protection to lm90_alert Sashiko reports: lm90_alert() executes in the smbus alert context and calls lm90updateconfreg() to disable the hardware alert line, without acquiring hwmon_lock. Concurrently, sysfs…
When was CVE-2026-64213 disclosed?
CVE-2026-64213 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64213 actively exploited?
CVE-2026-64213 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64213?
CVE-2026-64213 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64213, 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-64213

Explore →

Is Your Infrastructure Affected by CVE-2026-64213?

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

Start Free Scan →Browse All CVEs