Privilege escalation via stale NFC LLCP pointer
Published May 12, 2021 · Updated Sep 17, 2024
Use-after-free in Linux Kernel NFC LLCP sockets before 5.12.4 allows local users to elevate privileges by binding two sockets. llcp_sock_bind and llcp_sock_connect can assign one local object to two sockets, then release it without clearing llcp_sock->local, leaving a stale pointer used during closure. Typical configurations require CAP_NET_RAW; successful exploitation grants kernel-level privileges and can also crash the host.
Summary
What happened
Use-after-free in Linux Kernel NFC LLCP sockets before 5.12.4 allows local users to elevate privileges by binding two sockets. llcp_sock_bind and llcp_sock_connect can assign one local object to two sockets, then release it without clearing llcp_sock->local, leaving a stale pointer used during closure. Typical configurations require CAP_NET_RAW; successful exploitation grants kernel-level privileges and can also crash the host.
The record
- CVE
- CVE-2021-23134
- Published
- May 12, 2021
- Updated
- Sep 17, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 12, 2021CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=unspecified <5.12.4
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