CVE-2026-68467

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
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.8Exploit: 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:

mtd: mchp23k256: use SPI match data for chip caps

The driver stores chip capacity information in both the OF match table and the SPI id table. Probe currently uses of_device_get_match_data(), so a non-OF SPI modalias match falls back to mchp23k256_caps even when the SPI id table selected a different part.

Use spi_get_device_match_data() so SPI id-table driver_data is consumed when OF match data is absent. This keeps the existing default fallback while avoiding the wrong MTD geometry for id-table-only matches.

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

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

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

mtd: mchp23k256: use SPI match data for chip caps - kernel/git/stable/linux.git - Linux kernel stable tree

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

mtd: mchp23k256: use SPI match data for chip caps - kernel/git/stable/linux.git - Linux kernel stable tree

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

mtd: mchp23k256: use SPI match data for chip caps - kernel/git/stable/linux.git - Linux kernel stable tree

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

mtd: mchp23k256: use SPI match data for chip caps - kernel/git/stable/linux.git - Linux kernel stable tree

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

mtd: mchp23k256: use SPI match data for chip caps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e179b028da9fd628a09286a2c9df4fa076b2cc9
generic

mtd: mchp23k256: use SPI match data for chip caps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09e044192a42f716215fbd1a100ee87fa57426aa
generic

mtd: mchp23k256: use SPI match data for chip caps - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04ebd3766861f219325852c9598e0f0281cb3636

Vendor Advisories for CVE-2026-68467(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 27× in last 7d / 27× 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:33 UTCGHSA enrichment
  2. 2026-08-20 10:00 UTCGHSA enrichment
  3. 2026-08-19 21:27 UTCEG score recompute
  4. 2026-08-19 21:27 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 08:52 UTCGHSA enrichment
  7. 2026-08-18 20:19 UTCEG score recompute
  8. 2026-08-18 20:19 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 07:43 UTCGHSA enrichment
  12. 2026-08-17 19:07 UTCEG score recompute
  13. 2026-08-17 19:06 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:30 UTCEG score recompute
  16. 2026-08-17 06:30 UTCGHSA enrichment
  17. 2026-08-17 06:01 UTCEG score recompute▲ 7.80
  18. 2026-08-17 06:01 UTCGHSA enrichment
  19. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  20. 2026-08-17 05:35 UTCEG score recompute
  21. 2026-08-17 05:35 UTCGHSA enrichment
  22. 2026-08-17 05:25 UTCMITRE cvelistV5
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-15 06:20 UTCNVD update
Show 2 more
  1. 2026-08-15 06:20 UTCEG score recompute
  2. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68467?
CVE-2026-68467 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: mtd: mchp23k256: use SPI match data for chip caps The driver stores chip capacity information in both the OF match table and the SPI id table. Probe currently uses ofdevicegetmatchdata(), so a non-OF SPI modalias match falls back…
When was CVE-2026-68467 disclosed?
CVE-2026-68467 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-68467 actively exploited?
CVE-2026-68467 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68467?
CVE-2026-68467 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68467?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68467, 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-68467

Explore →

Is Your Infrastructure Affected by CVE-2026-68467?

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

Start Free Scan →Browse All CVEs