CVE-2026-64010: nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc()

Published Jul 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

nfc: llcp: Fix use-after-free race in nfcllcprecvcc()

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 nfcllcprecvcc() moves the socket from the connectingsockets list to the sockets list, it does so without holding the socket lock. If llcpsockrelease() is executing concurrently, it might have already unlinked the socket and dropped its references, which can result in nfcllcprecvcc() linking a freed socket into the live list.

Fix this by holding locksock() during the state transition and list movement in nfcllcprecvcc(). 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 recvhdlc() and recvdisc().

Affected Software

13 affected components
Linux Linux kernel
Linux Linux kernel>=3.6<5.10.259
Linux Linux kernel>=5.11<5.15.210
Linux Linux kernel>=5.16<6.1.176
Linux Linux kernel>=6.2<6.6.143
Linux Linux kernel>=6.7<6.12.93
Linux Linux kernel>=6.13<6.18.35
Linux Linux kernel>=6.19<7.0.12
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Hold lock_sock() during the state transition in nfc_llcp_recv_cc(), including checking that the socket is still hashed before moving it from the connecting_sockets list to the sockets list.

Event History

Jul 19, 2026
CVE Published
via MITRE·02:56 PM
Data Sourced
via MITRE·02:56 PM
DescriptionSeverity
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-64010?

CVE-2026-64010 has a risk rating of 35, indicating a moderate severity level.

2

What vulnerabilities are associated with CVE-2026-64010?

CVE-2026-64010 is associated with a use-after-free vulnerability and a race condition.

3

How do I fix CVE-2026-64010?

To fix CVE-2026-64010, ensure that your Linux kernel is updated to a version that includes the patch for this vulnerability.

4

What is affected by CVE-2026-64010?

CVE-2026-64010 affects the NFC LLCP connection state machine within the Linux kernel.

5

When was CVE-2026-64010 published?

CVE-2026-64010 was published on July 19, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203