CVE-2026-74315

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

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

lockd: Avoid hashing uninitialized bytes in nlm4svc_lookup_file()

file_hash() digests the first LOCKD_FH_HASH_SIZE bytes of nfs_fh.data when bucketing nlm_files[], independent of fh.size. Commit 3de744ee4e45 ("lockd: Use xdrgen XDR functions for the NLMv4 TEST procedure") set .pc_argzero to zero for the converted procedures and moved file-handle population into nlm4svc_lookup_file(), which copies only xdr_lock->fh.len bytes into lock->fh.data.

When an NLMv4 client presents a file handle shorter than LOCKD_FH_HASH_SIZE, bytes fh.len..31 retain whatever the argument buffer held from an earlier request. The same wire handle then hashes to different buckets across calls; nlm_lookup_file() misses the existing nlm_file entry, and lock-state lookups fail.

Zero only the tail bytes that file_hash() would otherwise consume. Handles of LOCKD_FH_HASH_SIZE or larger already populate every byte that file_hash() reads.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
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

lockd: Avoid hashing uninitialized bytes in nlm4svc_lookup_file() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e4c62caecf792e8a15ad9bc7f371e57c17e3302
generic

lockd: Avoid hashing uninitialized bytes in nlm4svc_lookup_file() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/686c2434f9f16b87aeed18d76cc562df9f2695ab

Vendor Advisories for CVE-2026-74315(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 47× in last 7d / 47× 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 02:06 UTCEG score recompute
  2. 2026-08-21 02:06 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 22:09 UTCGHSA enrichment
  5. 2026-08-20 18:11 UTCGHSA enrichment
  6. 2026-08-20 14:15 UTCGHSA enrichment
  7. 2026-08-20 10:19 UTCGHSA enrichment
  8. 2026-08-20 06:24 UTCGHSA enrichment
  9. 2026-08-20 02:28 UTCGHSA enrichment
  10. 2026-08-19 22:32 UTCGHSA enrichment
  11. 2026-08-19 18:35 UTCEG score recompute
  12. 2026-08-19 18:35 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 14:37 UTCGHSA enrichment
  15. 2026-08-19 10:41 UTCGHSA enrichment
  16. 2026-08-19 06:46 UTCGHSA enrichment
  17. 2026-08-19 02:47 UTCGHSA enrichment
  18. 2026-08-18 22:49 UTCGHSA enrichment
  19. 2026-08-18 18:54 UTCGHSA enrichment
  20. 2026-08-18 14:58 UTCEG score recompute
  21. 2026-08-18 14:57 UTCGHSA enrichment
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 10:44 UTCGHSA enrichment
  25. 2026-08-18 06:47 UTCGHSA enrichment
Show 22 more
  1. 2026-08-18 02:50 UTCGHSA enrichment
  2. 2026-08-17 22:54 UTCGHSA enrichment
  3. 2026-08-17 18:57 UTCGHSA enrichment
  4. 2026-08-17 14:19 UTCEG score recompute
  5. 2026-08-17 14:19 UTCGHSA enrichment
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 10:23 UTCEG score recompute
  8. 2026-08-17 10:23 UTCGHSA enrichment
  9. 2026-08-17 06:27 UTCEG score recompute
  10. 2026-08-17 06:27 UTCGHSA enrichment
  11. 2026-08-17 05:56 UTCEG score recompute 9.80
  12. 2026-08-17 05:56 UTCGHSA enrichment
  13. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-08-17 05:27 UTCEG score recompute
  15. 2026-08-17 05:27 UTCGHSA enrichment
  16. 2026-08-17 05:25 UTCMITRE cvelistV5
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 02:15 UTCEPSS rescore
  20. 2026-08-15 06:23 UTCNVD update
  21. 2026-08-15 06:16 UTCEG score recompute
  22. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74315?
CVE-2026-74315 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: lockd: Avoid hashing uninitialized bytes in nlm4svclookupfile() filehash() digests the first LOCKDFHHASHSIZE bytes of nfsfh.data when bucketing nlmfiles[], independent of fh.size. Commit 3de744ee4e45 ("lockd: Use xdrgen XDR…
When was CVE-2026-74315 disclosed?
CVE-2026-74315 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-74315 actively exploited?
CVE-2026-74315 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 68.7% of all scored CVEs.
What is the CVSS score of CVE-2026-74315?
CVE-2026-74315 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74315?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74315, 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-74315

Explore →

Is Your Infrastructure Affected by CVE-2026-74315?

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