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...

Description

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().

Metrics

CVSS 3.1

8.8/10

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

0.26%

17.1th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= a69f32af86e389dd232b1bb2269e202c1bfcc60f, < dce85215a6c7b0fd753f577a4c487f647119884c; >= a69f32af86e389dd232b1bb2269e202c1bfcc60f, < bd08bb7443c501d2f2a71d529e4afcf11c9b07d2; >= a69f32af86e389dd232b1bb2269e202c1bfcc60f, < 0b45c31746e1523d5d482fda8fcf54a35ac417f1; >= a69f32af86e389dd232b1bb2269e202c1bfcc60f, < ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2; >= a69f32af86e389dd232b1bb2269e202c1bfcc60f, < ad8a27d63cac96bac441edd002209ebd996e12fb; >= a69f32af86e389dd232b1bb2269e202c1bfcc60f, < 650bdd8fdfab64a09ee474150313dbc48c374795; >= a69f32af86e389dd232b1bb2269e202c1bfcc60f, < b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183; >= a69f32af86e389dd232b1bb2269e202c1bfcc60f, < b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77
Linux	Linux	3.6

References

Timeline

Published: Jul 19, 2026
Last Modified: Jul 30, 2026
Status: Awaiting Analysis

Frequently Asked Questions

What is 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().

How severe is CVE-2026-64010?

CVE-2026-64010 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 0.26% probability of exploitation in the next 30 days.

How do I fix CVE-2026-64010?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →