Kernel memory corruption via NFC socket reference race
Published Mar 2, 2024 · Updated Aug 5, 2026
Use-after-free in affected Linux kernel NFC LLCP receive processing allows physically proximate attackers to corrupt kernel memory via LLCP traffic. Socket lookup paths release their lock before acquiring a reference, permitting concurrent teardown to free the selected socket before later receive-path use. Exploitation requires an active NFC interface and attacker-controlled LLCP exchanges over a DEP link, enabling kernel-memory reads or writes, control-flow hijacking, or a kernel crash.
Summary
What happened
Use-after-free in affected Linux kernel NFC LLCP receive processing allows physically proximate attackers to corrupt kernel memory via LLCP traffic. Socket lookup paths release their lock before acquiring a reference, permitting concurrent teardown to free the selected socket before later receive-path use. Exploitation requires an active NFC interface and attacker-controlled LLCP exchanges over a DEP link, enabling kernel-memory reads or writes, control-flow hijacking, or a kernel crash.
The record
- CVE
- CVE-2023-52502
- Published
- Mar 2, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, CWE-362, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=8f50020ed9b81ba909ce9573f9d05263cdebf502 <31c07dffafce914c1d1543c135382a11ff058d93
- Affected versionversion=8f50020ed9b81ba909ce9573f9d05263cdebf502 <6ac22ecdaad2ecc662048f8c6b0ceb1ca0699ef9
- Affected versionversion=8f50020ed9b81ba909ce9573f9d05263cdebf502 <7adcf014bda16cdbf804af5c164d94d5d025db2d
- Affected versionversion=8f50020ed9b81ba909ce9573f9d05263cdebf502 <d1af8a39cf839d93c8967fdd858f6bbdc3e4a15c
- Affected versionversion=8f50020ed9b81ba909ce9573f9d05263cdebf502 <d888d3f70b0de32b4f51534175f039ddab15eef8
- Affected versionversion=8f50020ed9b81ba909ce9573f9d05263cdebf502 <e4f2611f07c87b3ddb57c4b9e8efcd1e330fc3dc
- Affected versionversion=8f50020ed9b81ba909ce9573f9d05263cdebf502 <e863f5720a5680e50c4cecf12424d7cc31b3eb0a
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
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