System crash via unlocked NFC device-list insertion
Published Mar 2, 2024 · Updated May 23, 2026
Improper locking in the Linux kernel NFC LLCP subsystem allows local users to corrupt the LLCP device list during device registration. nfc_llcp_register_device() calls list_add() on llcp_devices without holding llcp_devices_lock, allowing concurrent list modification. Triggering the race requires local low-privileged access and an NFC device-registration path; the demonstrated outcome is kernel list corruption and a crash.
Summary
What happened
Improper locking in the Linux kernel NFC LLCP subsystem allows local users to corrupt the LLCP device list during device registration. nfc_llcp_register_device() calls list_add() on llcp_devices without holding llcp_devices_lock, allowing concurrent list modification. Triggering the race requires local low-privileged access and an NFC device-registration path; the demonstrated outcome is kernel list corruption and a crash.
The record
- CVE
- CVE-2023-52524
- Published
- Mar 2, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 2, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=425d9d3a92df7d96b3cfb7ee5c240293a21cbde3 <7562780e32b84196731d57dd24563546fcf6d082
- Affected versionversion=5.10.188 <5.10.198
- Affected versionversion=5.15.121 <5.15.135
- Affected versionversion=5.4.251 <5.4.258
- Affected versionversion=6.1.39 <6.1.57
- Affected versionversion=6.3.13 <6.4
- Affected versionversion=6.4.4 <6.5
- Affected versionversion=6.5
- Affected versionversion=6709d4b7bc2e079241fdef15d1160581c5261c10 <29c16c2bf5866326d5fbc4a537b3997fcac23391
- Affected versionversion=6709d4b7bc2e079241fdef15d1160581c5261c10 <dfc7f7a988dad34c3bf4c053124fb26aa6c5f916
- Affected versionversion=96f2c6f272ec04083d828de46285a7d7b17d1aad <dba849cc98113b145c6e720122942c00b8012bdb
- Affected versionversion=b3ad46e155a6d91b36c6e892019a43e3ef3c696d
- Affected versionversion=dd6ff3f3862709ab1a12566e73b9d6a9b8f6e548 <191d87a19cf1005ecf41e1ae08d74e17379e8391
- Affected versionversion=e5207c1d69b1a9707615ab6ff9376e59fc096815
- Affected versionversion=fc8429f8d86801f092fbfbd257c3af821ac0dcd3 <4837a192f6d06d5bb2f3f47d6ce5353ab69bf86b
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
- syzbot C reproducer for corrupted LLCP device listfunctional · demonstrated
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