Local kernel panic via LLCP reference leak
Published May 26, 2021 · Updated Aug 4, 2024
Use-after-free in Linux Kernel NFC LLCP allows local users to crash the system by repeatedly binding a crafted LLCP socket. The llcp_sock_bind() failure paths retain the reference acquired by nfc_llcp_local_get() when allocation fails or no LLCP service access point is available, allowing repeated binds to wrap the reference count. A local low-privileged account must be able to create NFC LLCP sockets; successful triggering causes a kernel panic, while privilege escalation remains unverified.
Summary
What happened
Use-after-free in Linux Kernel NFC LLCP allows local users to crash the system by repeatedly binding a crafted LLCP socket. The llcp_sock_bind() failure paths retain the reference acquired by nfc_llcp_local_get() when allocation fails or no LLCP service access point is available, allowing repeated binds to wrap the reference count. A local low-privileged account must be able to create NFC LLCP sockets; successful triggering causes a kernel panic, while privilege escalation remains unverified.
The record
- CVE
- CVE-2020-25670
- Published
- May 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=All
What conditions does exploitation require?
What is affected?
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
- NFC LLCP repeated-bind trigger analysisproof of concept · 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