CVE-2026-68340

HIGHPre-NVD 7.77.7
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.7EG
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.7Exploit: 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: validate poll response sensor blocks

The OCC poll response parser walks a counted list of sensor data blocks. It used the static backing-array capacity as the parse boundary, but a transport response makes only data_length bytes current and valid. A truncated response can therefore make the parser consume a block header or block extent outside the current response.

Use data_length as the parent boundary, prove the fixed poll header and each current block header before reading them, and prove the complete block before advancing. Keep parsed sensor metadata local until the complete response has passed validation, then publish it. Propagate malformed-response errors before publishing the OCC as active.

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

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

hwmon: occ: validate poll response sensor blocks - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: occ: validate poll response sensor blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70e76e700fc6c46afb4e17aec099a1ea089b4a22
generic

hwmon: occ: validate poll response sensor blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54cb78eceb4e286ccd5a5c01a4632157860d47f0
generic

hwmon: occ: validate poll response sensor blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/538d862cc0dbd5c732fe26d5aad98eae039e6676
generic

hwmon: occ: validate poll response sensor blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/112525534ab5cff482d35897ca4ca11fd3a76f46

Vendor Advisories for CVE-2026-68340(2)

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 33× in last 7d / 45× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 18:29 UTCGHSA enrichment
  3. 2026-08-20 05:57 UTCGHSA enrichment
  4. 2026-08-19 17:24 UTCEG score recompute
  5. 2026-08-19 17:24 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:54 UTCEG score recompute
  8. 2026-08-19 16:54 UTCGHSA enrichment
  9. 2026-08-19 08:59 UTCGHSA enrichment
  10. 2026-08-18 20:25 UTCEG score recompute
  11. 2026-08-18 20:25 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 07:53 UTCGHSA enrichment
  15. 2026-08-17 19:20 UTCEG score recompute
  16. 2026-08-17 19:20 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:32 UTCEG score recompute
  19. 2026-08-17 06:32 UTCGHSA enrichment
  20. 2026-08-17 05:36 UTCEG score recompute
  21. 2026-08-17 05:36 UTCGHSA enrichment
  22. 2026-08-17 02:57 UTCEG score recompute
  23. 2026-08-17 02:57 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:25 UTCEG score recompute
Show 20 more
  1. 2026-08-16 14:25 UTCGHSA enrichment
  2. 2026-08-16 01:53 UTCGHSA enrichment
  3. 2026-08-15 13:21 UTCEG score recompute
  4. 2026-08-15 13:21 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-15 00:49 UTCGHSA enrichment
  7. 2026-08-14 12:17 UTCEG score recompute
  8. 2026-08-14 12:17 UTCGHSA enrichment
  9. 2026-08-13 23:45 UTCEG score recompute
  10. 2026-08-13 23:45 UTCGHSA enrichment
  11. 2026-08-13 23:04 UTCEG score recompute 7.70
  12. 2026-08-13 23:04 UTCGHSA enrichment
  13. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 08:43 UTCEG score recompute
  16. 2026-08-13 08:43 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-10 13:24 UTCNVD update
  19. 2026-08-10 12:18 UTCEG score recompute
  20. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68340?
CVE-2026-68340 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: hwmon: occ: validate poll response sensor blocks The OCC poll response parser walks a counted list of sensor data blocks. It used the static backing-array capacity as the parse boundary, but a transport response makes only…
When was CVE-2026-68340 disclosed?
CVE-2026-68340 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68340 actively exploited?
CVE-2026-68340 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 95.3% of all scored CVEs.
What is the CVSS score of CVE-2026-68340?
CVE-2026-68340 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-68340?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68340, 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-68340

Explore →

Is Your Infrastructure Affected by CVE-2026-68340?

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