Skip to main content

Linux Kernel CVE-2026-64010

| EUVDEUVD-2026-45583 HIGH
2026-07-19 Linux GHSA-6r5q-vq2q-562c
8.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.5 HIGH

NFC proximity gives AV:A; winning the concurrent CC-vs-release race raises complexity to AC:H; no auth needed (PR:N); kernel UAF yields high C/I/A.

3.1 AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 16:49 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
8.8 (HIGH)
Patch available
Jul 19, 2026 - 17:19 EUVD
CVE Published
Jul 19, 2026 - 14:56 cve.org
HIGH 8.8
CVE Published
Jul 19, 2026 - 14:56 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

AnalysisAI

Use-after-free in the Linux kernel NFC LLCP subsystem allows an adjacent attacker to corrupt kernel memory by racing a connection-complete (CC) packet against socket release in nfc_llcp_recv_cc(). Affected are kernels using the NFC Logical Link Control Protocol stack; successful exploitation of the race can yield kernel memory corruption leading to potential privilege escalation or denial of service. No public exploit identified at time of analysis, and EPSS probability is low (0.18%), consistent with a memory-safety race that is hard to trigger and requires NFC proximity.

Technical ContextAI

The flaw is in net/nfc/llcp of the Linux kernel, which implements NFC Forum's Logical Link Control Protocol (LLCP) used for peer-to-peer NFC communication. When a remote peer's connection-acceptance packet (CC) is received, nfc_llcp_recv_cc() migrates the associated socket from the connecting_sockets list to the live sockets list. The root cause is a classic time-of-check/use-after-free race (CWE-416 Use After Free, though the input lists CWE as N/A): the list movement was performed without holding lock_sock(), so a concurrent llcp_sock_release() could unlink the socket and drop its references, after which the recv path re-links an already-freed object into the live list. The fix acquires lock_sock() during the state transition and re-checks that the socket is still hashed before relinking, matching the locking discipline already used in recv_hdlc() and recv_disc().

RemediationAI

Vendor-released patch: upgrade to a fixed Linux kernel - 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 6.18.35, 7.0.12, or 7.1 (or later on your branch); consume the fix through your distribution's kernel update stream. The upstream fix commits are published at https://git.kernel.org/stable/c/dce85215a6c7b0fd753f577a4c487f647119884c and the parallel stable-branch commits listed in the references. Where immediate patching is not possible, the most effective compensating control is to remove the attack surface entirely: unload/blacklist the NFC and LLCP kernel modules (e.g. blacklist the 'nfc' and 'llcp' modules) or disable the NFC controller/hardware, which eliminates the vulnerable code path at the cost of losing all NFC peer-to-peer functionality (Android Beam-style transfers, NFC pairing). If NFC must remain enabled, restrict physical access so untrusted devices cannot be brought into NFC range, accepting that this does not fix the underlying race.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-64010 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy