Kernel memory corruption via repeated LLCP cleanup
Published Mar 27, 2025 · Updated Aug 5, 2026
Use-after-free in Linux kernel NFC LLCP allows local users to corrupt kernel memory by closing sockets after NFC device removal. local_cleanup() frees rx_pending during device unregister but leaves the pointer intact, so final LLCP socket release frees the same sk_buff again. An attacker must hold LLCP sockets while a local NFC device is unregistered; the second free can crash the kernel or enable kernel-level code execution.
Summary
What happened
Use-after-free in Linux kernel NFC LLCP allows local users to corrupt kernel memory by closing sockets after NFC device removal. local_cleanup() frees rx_pending during device unregister but leaves the pointer intact, so final LLCP socket release frees the same sk_buff again. An attacker must hold LLCP sockets while a local NFC device is unregistered; the second free can crash the kernel or enable kernel-level code execution.
The record
- CVE
- CVE-2023-53023
- Published
- Mar 27, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 27, 2025CVE 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=3536da06db0baa675f32de608c0a4c0f5ef0e9ff <4bb4db7f3187c6e3de6b229ffc87cdb30a2d22b6
- Affected versionversion=3536da06db0baa675f32de608c0a4c0f5ef0e9ff <54f7be61584b8ec4c6df405f479495b9397bae4a
- Affected versionversion=3536da06db0baa675f32de608c0a4c0f5ef0e9ff <7f129927feaf7c10b1c38bbce630172e9a08c834
- Affected versionversion=3536da06db0baa675f32de608c0a4c0f5ef0e9ff <a59cdbda3714e11aa3ab579132864c4c8c6d54f9
- Affected versionversion=3536da06db0baa675f32de608c0a4c0f5ef0e9ff <ad1baab3a5c03692d22ce446f38596a126377f6a
- Affected versionversion=3536da06db0baa675f32de608c0a4c0f5ef0e9ff <b09ae26f08aaf2d85f96ea7f90ddd3387f62216f
- Affected versionversion=3536da06db0baa675f32de608c0a4c0f5ef0e9ff <d3605282ec3502ec8847915eb2cf1f340493ff79
- Affected versionversion=3.9
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.
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