CVE-2026-74403

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:

crypto: ccp - Check for page allocation failure correctly in TIO

Sashiko notes:

> if __snp_alloc_firmware_pages() returns NULL under memory pressure, is it > safe to pass it directly to page_address()? > > On architectures without HASHED_PAGE_VIRTUAL, page_address(NULL) might > compute a deterministic but invalid, non-zero virtual address. The > subsequent if (tio_status) check would then evaluate to true, and > sev_tsm_init_locked() would dereference the invalid pointer.

Indeed, page_address(NULL) will return non-NULL garbage here. Fix this by checking the page allocation itself for NULL, not the resulting virtual address.

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
2%
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

crypto: ccp - Check for page allocation failure correctly in TIO - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: ccp - Check for page allocation failure correctly in TIO - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17e1aae19a06d9f6da4b46d54fa2aeab77ec0c69

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

Frequently asked(5)

What is CVE-2026-74403?
CVE-2026-74403 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Check for page allocation failure correctly in TIO Sashiko notes: if snpallocfirmware_pages() returns NULL under memory pressure, is it safe to pass it directly to page_address()? On architectures without…
When was CVE-2026-74403 disclosed?
CVE-2026-74403 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-74403 actively exploited?
CVE-2026-74403 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-74403?
CVE-2026-74403 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74403?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74403, 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-74403

Explore →

Is Your Infrastructure Affected by CVE-2026-74403?

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

Start Free Scan →Browse All CVEs