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… (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().
AI Analysis
Technical Summary
CVE-2026-64010 describes a race condition in the Linux kernel's NFC LLCP implementation where nfc_llcp_recv_cc() processes the connection acceptance packet without holding the socket lock. Concurrent execution of llcp_sock_release() can unlink and free the socket, causing nfc_llcp_recv_cc() to use a freed socket object. The vulnerability is fixed by acquiring lock_sock() during the state transition and verifying the socket's hashed state before proceeding, aligning the locking pattern with other similar functions.
Potential Impact
This vulnerability can lead to a use-after-free condition in kernel memory, which may cause system instability or crashes. The description does not specify privilege escalation or remote code execution impacts. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available and has been applied to the Linux kernel source code. Users should update to the fixed kernel versions once released by their distribution vendors. Patch status is not explicitly stated in the provided data; check vendor advisories for the exact fixed versions and update instructions.
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… (CVE-2026-64010)
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().
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-64010 describes a race condition in the Linux kernel's NFC LLCP implementation where nfc_llcp_recv_cc() processes the connection acceptance packet without holding the socket lock. Concurrent execution of llcp_sock_release() can unlink and free the socket, causing nfc_llcp_recv_cc() to use a freed socket object. The vulnerability is fixed by acquiring lock_sock() during the state transition and verifying the socket's hashed state before proceeding, aligning the locking pattern with other similar functions.
Potential Impact
This vulnerability can lead to a use-after-free condition in kernel memory, which may cause system instability or crashes. The description does not specify privilege escalation or remote code execution impacts. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available and has been applied to the Linux kernel source code. Users should update to the fixed kernel versions once released by their distribution vendors. Patch status is not explicitly stated in the provided data; check vendor advisories for the exact fixed versions and update instructions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6r5q-vq2q-562c
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64010"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27aa2a4a8d598912d8ad
Added to database: 07/19/2026, 19:38:18 UTC
Last enriched: 07/19/2026, 19:59:55 UTC
Last updated: 07/20/2026, 21:51:11 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.