CVE-2026-64010·Kernel vulnerability
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().
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.12
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.20% — higher than 9% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-64010 scores 8.8 on CVSS, so a successful attack would be serious — but at 0.20%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.12
Fixed in: 7.0.12
How to fix this CVE
Update your Linux kernel to version 7.0.12 or later to patch a use-after-free vulnerability in the NFC LLCP subsystem. This race condition affects kernel versions 6.19 through 7.0.11 and can be triggered through concurrent NFC connection state transitions. Apply the kernel update immediately and reboot to ensure the patch is active.
sudo dnf update kernel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Run 'uname -r' to check the current kernel version and confirm if it falls within the vulnerable range (6.19 to 7.0.11)
- Execute 'cat /proc/net/nfc' to verify if NFC LLCP subsystem is loaded; if the file is empty or doesn't exist, NFC is not actively configured
- Check kernel logs for NFC-related errors using 'sudo dmesg | grep -i nfc' or 'sudo journalctl -u kernel | grep nfc' to identify any LLCP connection state machine anomalies
- After applying the patch, run 'uname -r' again and verify the kernel version is 7.0.12 or higher, then check 'cat /proc/version' to confirm the update is reflected in the running kernel
FAQ
What is CVE-2026-64010?
CVE-2026-64010 is a use-after-free race condition in the Linux kernel's NFC LLCP (Logical Link Control and Multiplexing) subsystem. The vulnerability occurs when an NFC connection acceptance packet (CC) is processed concurrently with socket release, potentially allowing a freed socket object to be relinked into an active connection list, leading to memory corruption or denial of service.
Is CVE-2026-64010 being actively exploited?
No, CVE-2026-64010 is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploit code is currently available. However, the high CVSS score of 8.8 indicates significant risk if triggered.
What versions of Kernel are affected by CVE-2026-64010?
Linux kernel versions 6.19 through 7.0.11 are affected. The vulnerability has been resolved in version 7.0.12 and later stable releases.
How do I check if my server is vulnerable to CVE-2026-64010?
Run 'uname -r' to display your kernel version. If the output shows a version between 6.19 and 7.0.11 (inclusive), your system is vulnerable. Cross-reference with 'cat /proc/version' for confirmation.
Does Defensia detect CVE-2026-64010?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-64010 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/0b45c31746e1523d5d482fda8fcf54a35ac417f1
- https://git.kernel.org/stable/c/650bdd8fdfab64a09ee474150313dbc48c374795
- https://git.kernel.org/stable/c/ad8a27d63cac96bac441edd002209ebd996e12fb
- https://git.kernel.org/stable/c/b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183
- https://git.kernel.org/stable/c/b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-64010. Free for 1 server.
Get started free