CVE-2026-68473

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/uaccess: correct check for CONFIG_PPC_E500 in mask_user_address()

mask_user_address() incorrectly checks for CONFIG_E500 instead of CONFIG_PPC_E500, causing mask_user_address_isel() to not be used on E500 hardware. Fix the check to use the correct name.

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

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (2)

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

powerpc/uaccess: correct check for CONFIG_PPC_E500 in mask_user_address() - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/uaccess: correct check for CONFIG_PPC_E500 in mask_user_address() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d5c234774a82f27b594f70c15fc45ce3648e4295

Vendor Advisories for CVE-2026-68473(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 06:30 UTCEG score recompute
  2. 2026-08-21 06:30 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 18:35 UTCGHSA enrichment
  5. 2026-08-20 06:40 UTCGHSA enrichment
  6. 2026-08-19 18:45 UTCEG score recompute
  7. 2026-08-19 18:45 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 06:49 UTCGHSA enrichment
  10. 2026-08-18 18:54 UTCEG score recompute
  11. 2026-08-18 18:54 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 06:58 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-68473?
CVE-2026-68473 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc/uaccess: correct check for CONFIGPPCE500 in maskuseraddress() maskuseraddress() incorrectly checks for CONFIG_E500 instead of CONFIGPPCE500, causing maskuseraddress_isel() to not be used on E500 hardware. Fix the check to…
When was CVE-2026-68473 disclosed?
CVE-2026-68473 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-68473 actively exploited?
CVE-2026-68473 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 94.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68473?
CVE-2026-68473 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68473?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68473, 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-68473

Explore →

Is Your Infrastructure Affected by CVE-2026-68473?

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

Start Free Scan →Browse All CVEs