CVE-2026-74567

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

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

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

keys: fix out-of-bounds read in keyring_get_key_chunk()

For description-level chunks keyring_get_key_chunk() advances the read pointer by level * sizeof(long) past the inline prefix but only bounds-checks the prefix, so a long enough key description is read past its kmemdup(desc, desc_len + 1) allocation. Compute the full byte offset and bounds-check the description against it before reading.

The walk only reaches a description-level chunk when two keys collide through the hash, x, type and domain_tag chunks, so this is reached from an unprivileged add_key(2) with a crafted pair of same-type keys whose index hashes collide; KASAN reports a slab-out-of-bounds read.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
36(Track)
EG Risk 36/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
Severity71% × 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 19, 2026

Advisory Details (5)

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

keys: fix out-of-bounds read in keyring_get_key_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

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

keys: fix out-of-bounds read in keyring_get_key_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

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

keys: fix out-of-bounds read in keyring_get_key_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8dba33c1e779d0fb9a2acb31e354cf0fc0229111
generic

keys: fix out-of-bounds read in keyring_get_key_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63918731f9ae25b5deb022f118e941e6dddfcef4
generic

keys: fix out-of-bounds read in keyring_get_key_chunk() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-74567(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 29× in last 7d / 29× 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:05 UTCEG score recompute
  2. 2026-08-21 06:05 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 17:56 UTCGHSA enrichment
  5. 2026-08-20 05:47 UTCGHSA enrichment
  6. 2026-08-19 17:38 UTCEG score recompute
  7. 2026-08-19 17:38 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:52 UTCEG score recompute
  10. 2026-08-19 16:52 UTCGHSA enrichment
  11. 2026-08-19 07:22 UTCGHSA enrichment
  12. 2026-08-18 19:13 UTCGHSA enrichment
  13. 2026-08-18 07:03 UTCGHSA enrichment
  14. 2026-08-17 18:53 UTCEG score recompute
  15. 2026-08-17 18:53 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:23 UTCEG score recompute
  18. 2026-08-17 06:23 UTCGHSA enrichment
  19. 2026-08-17 05:54 UTCEG score recompute 7.10
  20. 2026-08-17 05:54 UTCGHSA enrichment
  21. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  22. 2026-08-17 05:39 UTCEG score recompute
  23. 2026-08-17 05:39 UTCGHSA enrichment
  24. 2026-08-17 05:39 UTCMITRE cvelistV5
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 4 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-15 13:27 UTCNVD update
  3. 2026-08-15 12:38 UTCEG score recompute
  4. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74567?
CVE-2026-74567 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: keys: fix out-of-bounds read in keyringgetkey_chunk() For description-level chunks keyringgetkey_chunk() advances the read pointer by level * sizeof(long) past the inline prefix but only bounds-checks the prefix, so a long enough…
When was CVE-2026-74567 disclosed?
CVE-2026-74567 was first published in the National Vulnerability Database on August 15, 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-74567 actively exploited?
CVE-2026-74567 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-74567?
CVE-2026-74567 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-74567?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74567, 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-74567

Explore →

Is Your Infrastructure Affected by CVE-2026-74567?

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