← All Advisories

CVE-2026-64010

Last refreshed2026-10-13

Status: UPDATED  |  Advisory ID: CVE-2026-64010

Key Details

CVECVE-2026-64010
CVSS Score / Version
8.8 (High) / CVSS v3.1
Updated2026-10-13
CVSS Vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is adjacent; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-64010
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-64010