CVE-2026-31770

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

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: (occ) Fix division by zero in occ_show_power_1()

In occ_show_power_1() case 1, the accumulator is divided by update_tag without checking for zero. If no samples have been collected yet (e.g. during early boot when the sensor block is included but hasn't been updated), update_tag is zero, causing a kernel divide-by-zero crash.

The 2019 fix in commit 211186cae14d ("hwmon: (occ) Fix division by zero issue") only addressed occ_get_powr_avg() used by occ_show_power_2() and occ_show_power_a0(). This separate code path in occ_show_power_1() was missed.

Fix this by reusing the existing occ_get_powr_avg() helper, which already handles the zero-sample case and uses mul_u64_u32_div() to multiply before dividing for better precision. Move the helper above occ_show_power_1() so it is visible at the call site.

[groeck: Fix alignment problems reported by checkpatch]

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

May 1, 2026

Last Modified

May 11, 2026

Advisory Details (8)

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

hwmon: (occ) Fix division by zero in occ_show_power_1() - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (occ) Fix division by zero in occ_show_power_1() - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (occ) Fix division by zero in occ_show_power_1() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b89ce0c98bf3015f493ca4285b2d1056cd8c733
generic

hwmon: (occ) Fix division by zero in occ_show_power_1() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53e6175756b8c474b6247bbcea0aad3d68357475
generic

hwmon: (occ) Fix division by zero in occ_show_power_1() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39e2a5bf970402a8530a319cf06122e216ba57b8
generic

hwmon: (occ) Fix division by zero in occ_show_power_1() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37ae8fadc74ed68e5bc364ffd17746d88e449ae3
generic

hwmon: (occ) Fix division by zero in occ_show_power_1() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2502684b9e835de9a992ec47c3e6c6faabe3858d
generic

hwmon: (occ) Fix division by zero in occ_show_power_1() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/243d55bd3f08cb15eee9d63f4716d4d4cdd760f5

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1—

Weakness Classification(1)

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

All Vendor Advisories

(24)

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 5× in last 7d / 32× 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.

Showing the most recent 100 of 208 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-04 00:59 UTCOSV refresh
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:17 UTCEPSS rescore
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-17 13:43 UTCEG score recompute
  5. 2026-08-17 13:43 UTCVendor advisory
  6. 2026-08-17 13:43 UTCGHSA enrichment
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 05:17 UTCEG score recompute
  9. 2026-08-16 05:17 UTCVendor advisory
  10. 2026-08-16 05:17 UTCGHSA enrichment
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 03:46 UTCEG score recompute
  14. 2026-08-14 03:46 UTCVendor advisory
  15. 2026-08-14 03:46 UTCGHSA enrichment
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 17:24 UTCEG score recompute
  18. 2026-08-12 17:24 UTCVendor advisory
  19. 2026-08-12 17:24 UTCGHSA enrichment
  20. 2026-08-12 13:50 UTCEPSS rescore
  21. 2026-08-11 02:48 UTCEG score recompute
  22. 2026-08-11 02:48 UTCVendor advisory
  23. 2026-08-11 02:48 UTCGHSA enrichment
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 02:50 UTCEG score recompute
  26. 2026-08-10 02:50 UTCVendor advisory
  27. 2026-08-10 02:50 UTCGHSA enrichment
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 02:53 UTCVendor advisory
  30. 2026-08-09 02:53 UTCGHSA enrichment
  31. 2026-08-08 02:30 UTCEG score recompute
  32. 2026-08-08 02:30 UTCVendor advisory
  33. 2026-08-08 02:30 UTCGHSA enrichment
  34. 2026-08-07 02:32 UTCEG score recompute
  35. 2026-08-07 02:32 UTCVendor advisory
  36. 2026-08-07 02:32 UTCGHSA enrichment
  37. 2026-08-06 13:46 UTCEPSS rescore
  38. 2026-08-05 22:35 UTCEG score recompute
  39. 2026-08-05 22:35 UTCVendor advisory
  40. 2026-08-05 22:35 UTCGHSA enrichment
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-04 15:10 UTCEPSS rescore
  43. 2026-08-04 10:38 UTCEPSS rescore
  44. 2026-08-03 20:22 UTCEG score recompute
  45. 2026-08-03 20:22 UTCVendor advisory
  46. 2026-08-03 20:22 UTCGHSA enrichment
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-02 05:39 UTCEG score recompute
  49. 2026-08-02 05:39 UTCVendor advisory
  50. 2026-08-02 05:39 UTCGHSA enrichment
  51. 2026-08-02 02:27 UTCEPSS rescore
  52. 2026-08-01 04:16 UTCEPSS rescore
  53. 2026-07-30 16:28 UTCEPSS rescore
  54. 2026-07-30 01:30 UTCEPSS rescore
  55. 2026-07-28 15:36 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-26 14:54 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-25 14:17 UTCEPSS rescore
  60. 2026-07-24 14:17 UTCEPSS rescore
  61. 2026-07-23 14:18 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 03:08 UTCEG score recompute
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-21 15:24 UTCEPSS rescore
  68. 2026-07-20 17:08 UTCEPSS rescore
  69. 2026-07-20 17:08 UTCEPSS rescore
  70. 2026-07-19 19:48 UTCOSV refresh
  71. 2026-07-19 14:31 UTCEPSS rescore
  72. 2026-07-19 14:31 UTCEPSS rescore
  73. 2026-07-19 02:29 UTCEPSS rescore
  74. 2026-07-18 10:04 UTCEPSS rescore
  75. 2026-07-18 10:04 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31770?
CVE-2026-31770 is a medium vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: hwmon: (occ) Fix division by zero in occshowpower_1() In occshowpower_1() case 1, the accumulator is divided by update_tag without checking for zero. If no samples have been collected yet (e.g. during early boot when the sensor…
When was CVE-2026-31770 disclosed?
CVE-2026-31770 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 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-31770 actively exploited?
CVE-2026-31770 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-31770?
CVE-2026-31770 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31770?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31770, 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-31770

Explore →

Is Your Infrastructure Affected by CVE-2026-31770?

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

Start Free Scan →Browse All CVEs