Kernel memory corruption via unlocked LLCP transition
Published Jul 19, 2026 · Updated Jul 19, 2026
Use-after-free in affected Linux kernel NFC LLCP releases allows physically proximate attackers to corrupt memory during CC packet processing. The nfc_llcp_recv_cc() path moves a socket between connection lists without its socket lock, while llcp_sock_release() can concurrently unlink and free it. Exploitation requires NFC hardware and a concurrent socket release; the published record does not establish a specific outcome beyond unsafe reuse of the freed socket.
Summary
What happened
Use-after-free in affected Linux kernel NFC LLCP releases allows physically proximate attackers to corrupt memory during CC packet processing. The nfc_llcp_recv_cc() path moves a socket between connection lists without its socket lock, while llcp_sock_release() can concurrently unlink and free it. Exploitation requires NFC hardware and a concurrent socket release; the published record does not establish a specific outcome beyond unsafe reuse of the freed socket.
The record
- CVE
- CVE-2026-64010
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.6
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <0b45c31746e1523d5d482fda8fcf54a35ac417f1
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <650bdd8fdfab64a09ee474150313dbc48c374795
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <ad8a27d63cac96bac441edd002209ebd996e12fb
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <b2a60f7f846faaf5c2cdad4ea6d3a33e5f863183
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <b493ea2765cc17cb8aa7e7544a4b6dcb05b6ed77
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <bd08bb7443c501d2f2a71d529e4afcf11c9b07d2
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <dce85215a6c7b0fd753f577a4c487f647119884c
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <ee2d1a8a1833c5e56e9a1745e64b0b4edda732c2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo