CVE-2026-64011

Analyzed Analyzed - Analysis Complete

Use-After-Free in Linux Kernel NFC LLCP Socket

Publication date: 2026-07-19

Last updated on: 2026-10-13

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix use-after-free in llcp_sock_release() llcp_sock_release() unconditionally unlinks the socket from the local sockets list. However, if the socket is still in connecting state, it is on the connecting list. Fix this by checking the socket state and unlinking from the correct list.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-19

Last Modified

2026-10-13

Generated

2026-10-19

AI Q&A

2026-07-19

EPSS Evaluated

2026-10-18

NVD

CVE-2026-64011

EUVD

EUVD-2026-45584

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	7.1
linux	linux_kernel	From 5.16 (inc) to 6.1.176 (exc)
linux	linux_kernel	From 6.13 (inc) to 6.18.35 (exc)
linux	linux_kernel	From 6.2 (inc) to 6.6.143 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.93 (exc)
linux	linux_kernel	From 5.11 (inc) to 5.15.210 (exc)
linux	linux_kernel	7.1
linux	linux_kernel	From 6.19 (inc) to 7.0.12 (exc)
linux	linux_kernel	From 3.10.10 (inc) to 5.10.259 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This vulnerability is a use-after-free bug in the Linux kernel's NFC LLCP (Near Field Communication Logical Link Control Protocol) implementation. The issue occurs in the llcp_sock_release() function, which incorrectly unlinks a socket from the local sockets list even when the socket is still in a connecting state. This can lead to the socket being freed while still in use, causing a use-after-free condition.

Detection Guidance

This vulnerability is specific to the Linux kernel's NFC LLCP socket implementation and may not have direct network detection commands. Check kernel logs for crashes or errors related to nfc or llcp_sock_release using dmesg or journalctl. Ensure your kernel is updated to a patched version.

Impact Analysis

This vulnerability could allow an attacker to cause a denial-of-service condition or potentially execute arbitrary code on a system with a vulnerable Linux kernel. Systems using NFC LLCP functionality may be affected, leading to system crashes or unauthorized access if exploited.

Compliance Impact

This vulnerability is a use-after-free issue in the Linux kernel's NFC LLCP socket release mechanism. It does not directly impact compliance with standards like GDPR or HIPAA, as those focus on data protection, privacy, and security controls rather than kernel-level socket management.

Mitigation Strategies

Update your Linux kernel to the latest stable version that includes the fix for this vulnerability. If immediate patching is not possible, consider disabling NFC functionality temporarily until the update is applied.

Hi! I’m here to help you understand CVE-2026-64011. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70