CVE-2026-64010
In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() A race condition exists in the NFC LLCP connection state machine where the connection acceptance packet (CC) can be processed concurrently with socket release. This can lead to a use-after-free of the socket object. When nfc_llcp_recv_cc() moves the socket from the connecting_sockets list to the sockets list, it does so without holding the socket lock. If llcp_sock_release() is executing concurrently, it might have already unlinked the socket and dropped its references, which can result in nfc_llcp_recv_cc() linking a freed socket into the live list. Fix this by holding lock_sock() during the state transition and list movement in nfc_llcp_recv_cc(). After acquiring the lock, check if the socket is still hashed to ensure it hasn't already been unlinked and marked for destruction by the release path. This aligns the locking pattern with recv_hdlc() and recv_disc().
Affected versions
Linux kernel versions
3.6
and later are affected. Fixed in
5.10.259,
5.15.210,
6.1.176,
6.6.143,
6.12.93,
6.18.35,
7.0.12,
7.1
and their respective stable series.
References
8 totalFrequently asked questions
-
What is CVE-2026-64010?
CVE-2026-64010 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 3.6 onward and has been patched in 5.10.259, 5.15.210, 6.1.176 and others. CVE-2026-64010 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-64010?
Yes — CVE-2026-64010 has been patched. Fixed versions include 5.10.259, 5.15.210, 6.1.176 and others. If you are running Linux kernel 3.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-64010 actively exploited?
No — CVE-2026-64010 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.