CVE-2026-64523

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, 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:

net/handshake: Take a long-lived file reference at submit

handshake_nl_accept_doit() needs the file pointer backing req->hr_sk->sk_socket to survive the window between handshake_req_next() and the subsequent FD_PREPARE() and get_file(). The submit-side sock_hold() does not provide that. sk_refcnt keeps struct sock alive, but struct socket is owned by sock->file: when the consumer fputs the last file reference, sock_release() tears the socket down regardless of any sock_hold.

Add an hr_file pointer to struct handshake_req and acquire an explicit reference on sock->file during handshake_req_submit(). handshake_complete() and handshake_req_cancel() release the reference on the completion-bit-winning path.

The submit error path must also release the file reference, but after rhashtable insertion a concurrent handshake_req_cancel() can discover the request and race the error path. Gate the error-path cleanup -- sk_destruct restoration, fput, and request destruction -- with test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED), the same serialization handshake_complete() and handshake_req_cancel() already use. When cancel has already claimed ownership, the submit error path returns without touching the request; socket teardown handles final destruction.

The accept-side dereferences are not yet retargeted; that change comes in the next patch.

CVSS v3
9.8
EG Score
9.8(medium)
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
5%
KEV
Not listed

Published

July 25, 2026

Last Modified

July 27, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

net/handshake: Take a long-lived file reference at submit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/685b10dd0e32c7782cead16c8cf055c609678583
generic

net/handshake: Take a long-lived file reference at submit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16eaba5aa89c04eea125905bb8f988c1897f4f29
generic

net/handshake: Take a long-lived file reference at submit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09dba37eee70d0596e26645015f1aa95a9848e9d

Vendor Advisories for CVE-2026-64523(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 14× in last 7d / 14× 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-07-27 05:26 UTCEG score recompute
  2. 2026-07-27 05:26 UTCGHSA enrichment
  3. 2026-07-27 05:13 UTCEG score recompute 9.80
  4. 2026-07-27 05:13 UTCGHSA enrichment
  5. 2026-07-27 05:12 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 02:45 UTCEG score recompute
  9. 2026-07-26 02:45 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-25 10:39 UTCNVD update
  13. 2026-07-25 10:02 UTCEG score recompute
  14. 2026-07-25 10:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64523?
CVE-2026-64523 is a critical vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net/handshake: Take a long-lived file reference at submit handshakenlaccept_doit() needs the file pointer backing req->hrsk->sksocket to survive the window between handshakereqnext() and the subsequent FDPREPARE() and getfile().…
When was CVE-2026-64523 disclosed?
CVE-2026-64523 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64523 actively exploited?
CVE-2026-64523 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-64523?
CVE-2026-64523 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64523?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64523, 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-64523

Explore →

Is Your Infrastructure Affected by CVE-2026-64523?

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