CVE-2026-68474

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:

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access()

spufs_mem_mmap_access() computes the local store offset as address - vma->vm_start, but bounds-checks it against vma->vm_end instead of the local store size. On 64-bit, offset is always well below vma->vm_end, so the clamp never fires and len stays unbounded against the LS_SIZE buffer returned by ctx->ops->get_ls().

Reject offsets at or beyond LS_SIZE and clamp len to the remaining space, mirroring the guard already used by spufs_mem_mmap_fault() and spufs_ps_fault().

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
6%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d3569bfdceda69d5ffd5148901e57b69954d9ef
generic

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/913feef74354c653f10ecd4631df7618a95c49c2
generic

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4efa313b15925bdd864784865d6585174979294b
generic

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/47b87f469a35b5ffc81c16eee6b13a9b6c8d55c6
generic

powerpc/spufs: fix out-of-bounds access in spufs_mem_mmap_access() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c1e92f75e11a11492b8cb901fceeb9f16ae6415

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

Frequently asked(5)

What is CVE-2026-68474?
CVE-2026-68474 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc/spufs: fix out-of-bounds access in spufsmemmmap_access() spufsmemmmap_access() computes the local store offset as address - vma->vmstart, but bounds-checks it against vma->vmend instead of the local store size. On 64-bit,…
When was CVE-2026-68474 disclosed?
CVE-2026-68474 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-68474 actively exploited?
CVE-2026-68474 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 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68474?
CVE-2026-68474 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68474?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68474, 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-68474

Explore →

Is Your Infrastructure Affected by CVE-2026-68474?

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