CVE-2026-64523

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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

A fix is available — apply it.

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

Published

July 25, 2026

Last Modified

August 9, 2026

Advisory Details (4)

Auto-updated Sep 13, 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/b913801ad9b9a51437d84d030ec6843e08976bd6
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(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 62× in last 7d / 276× 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.

Showing the most recent 100 of 574 total refreshes for this CVE.

  1. 2026-09-15 09:18 UTCEG score recompute
  2. 2026-09-15 09:18 UTCVendor advisory
  3. 2026-09-15 09:18 UTCGHSA enrichment
  4. 2026-09-14 16:00 UTCVendor advisory
  5. 2026-09-14 16:00 UTCGHSA enrichment
  6. 2026-09-14 12:17 UTCVendor advisory
  7. 2026-09-14 12:17 UTCGHSA enrichment
  8. 2026-09-14 08:35 UTCVendor advisory
  9. 2026-09-14 08:35 UTCGHSA enrichment
  10. 2026-09-14 04:51 UTCVendor advisory
  11. 2026-09-14 04:51 UTCGHSA enrichment
  12. 2026-09-14 01:09 UTCVendor advisory
  13. 2026-09-14 01:08 UTCGHSA enrichment
  14. 2026-09-13 21:23 UTCEG score recompute
  15. 2026-09-13 21:23 UTCVendor advisory
  16. 2026-09-13 21:23 UTCGHSA enrichment
  17. 2026-09-13 15:22 UTCVendor advisory
  18. 2026-09-13 15:22 UTCGHSA enrichment
  19. 2026-09-13 11:16 UTCVendor advisory
  20. 2026-09-13 11:16 UTCGHSA enrichment
  21. 2026-09-13 07:34 UTCVendor advisory
  22. 2026-09-13 07:34 UTCGHSA enrichment
  23. 2026-09-13 03:51 UTCVendor advisory
  24. 2026-09-13 03:51 UTCGHSA enrichment
  25. 2026-09-13 00:08 UTCVendor advisory
Show 75 more
  1. 2026-09-13 00:07 UTCGHSA enrichment
  2. 2026-09-12 20:23 UTCVendor advisory
  3. 2026-09-12 20:23 UTCGHSA enrichment
  4. 2026-09-12 16:35 UTCEG score recompute
  5. 2026-09-12 16:35 UTCVendor advisory
  6. 2026-09-12 16:35 UTCGHSA enrichment
  7. 2026-09-12 12:52 UTCVendor advisory
  8. 2026-09-12 12:52 UTCGHSA enrichment
  9. 2026-09-12 09:08 UTCVendor advisory
  10. 2026-09-12 09:08 UTCGHSA enrichment
  11. 2026-09-12 04:55 UTCVendor advisory
  12. 2026-09-12 04:55 UTCGHSA enrichment
  13. 2026-09-12 00:45 UTCVendor advisory
  14. 2026-09-12 00:45 UTCGHSA enrichment
  15. 2026-09-11 20:27 UTCVendor advisory
  16. 2026-09-11 20:27 UTCGHSA enrichment
  17. 2026-09-11 16:20 UTCEG score recompute
  18. 2026-09-11 16:20 UTCVendor advisory
  19. 2026-09-11 16:20 UTCGHSA enrichment
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 09:37 UTCEPSS rescore
  22. 2026-09-11 07:09 UTCVendor advisory
  23. 2026-09-11 07:09 UTCGHSA enrichment
  24. 2026-09-11 02:08 UTCVendor advisory
  25. 2026-09-11 02:07 UTCGHSA enrichment
  26. 2026-09-10 20:51 UTCVendor advisory
  27. 2026-09-10 20:51 UTCGHSA enrichment
  28. 2026-09-10 14:41 UTCVendor advisory
  29. 2026-09-10 14:41 UTCGHSA enrichment
  30. 2026-09-10 10:24 UTCEG score recompute
  31. 2026-09-10 10:24 UTCVendor advisory
  32. 2026-09-10 10:24 UTCGHSA enrichment
  33. 2026-09-09 12:11 UTCVendor advisory
  34. 2026-09-09 12:11 UTCGHSA enrichment
  35. 2026-09-09 08:29 UTCEG score recompute
  36. 2026-09-09 08:29 UTCVendor advisory
  37. 2026-09-09 08:28 UTCGHSA enrichment
  38. 2026-09-08 22:01 UTCEPSS rescore
  39. 2026-09-08 00:54 UTCVendor advisory
  40. 2026-09-08 00:54 UTCGHSA enrichment
  41. 2026-09-07 21:10 UTCEG score recompute
  42. 2026-09-07 21:10 UTCVendor advisory
  43. 2026-09-07 21:10 UTCGHSA enrichment
  44. 2026-09-07 16:01 UTCEPSS rescore
  45. 2026-09-06 23:59 UTCVendor advisory
  46. 2026-09-06 23:59 UTCGHSA enrichment
  47. 2026-09-06 15:40 UTCEG score recompute
  48. 2026-09-06 15:40 UTCVendor advisory
  49. 2026-09-06 15:40 UTCGHSA enrichment
  50. 2026-09-06 13:47 UTCEPSS rescore
  51. 2026-09-06 11:38 UTCVendor advisory
  52. 2026-09-06 11:37 UTCGHSA enrichment
  53. 2026-09-06 07:53 UTCVendor advisory
  54. 2026-09-06 07:53 UTCGHSA enrichment
  55. 2026-09-06 02:45 UTCVendor advisory
  56. 2026-09-06 02:44 UTCGHSA enrichment
  57. 2026-09-05 23:01 UTCVendor advisory
  58. 2026-09-05 23:01 UTCGHSA enrichment
  59. 2026-09-05 19:18 UTCEG score recompute
  60. 2026-09-05 19:18 UTCVendor advisory
  61. 2026-09-05 19:17 UTCGHSA enrichment
  62. 2026-09-05 15:31 UTCEPSS rescore
  63. 2026-09-05 09:37 UTCVendor advisory
  64. 2026-09-05 09:37 UTCGHSA enrichment
  65. 2026-09-05 05:54 UTCVendor advisory
  66. 2026-09-05 05:54 UTCGHSA enrichment
  67. 2026-09-04 16:22 UTCEG score recompute
  68. 2026-09-04 16:22 UTCVendor advisory
  69. 2026-09-04 16:22 UTCGHSA enrichment
  70. 2026-09-04 12:37 UTCEG score recompute
  71. 2026-09-04 12:37 UTCGHSA enrichment
  72. 2026-09-04 05:07 UTCEPSS rescore
  73. 2026-09-02 14:12 UTCEPSS rescore
  74. 2026-09-01 23:06 UTCEG score recompute
  75. 2026-09-01 23:06 UTCVendor advisory

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 August 9, 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 70.7% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.