Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-64523Published 2026-07-25

CVE-2026-64523 — Linux

As of 2026-07-25, CVE-2026-64523 is a vulnerability in Linux, EPSS 0.1% (5.1th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-64523 as of 2026-07-25; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS
—Not yet scored
EPSS
0.1%Higher than 5.1% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
0.2/10Threadlinqs triage score
Published
EPSS 0.1% (higher than 5.1% of all scored CVEs) · Priority 0.2/10 · Published 2026-07-25

Last updated:

What is CVE-2026-64523?

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.

1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 72 days ago.

Severity and exploitation probability

EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 5.1% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
0.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-25

Is CVE-2026-64523 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-64523

No vendor patch reference has been recorded for CVE-2026-64523 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-64523

No threat campaign in the Threadlinqs corpus currently references CVE-2026-64523, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Other references