Local privilege escalation via LLCP reference leak
Published May 26, 2021 · Updated Aug 4, 2024
Use-after-free in the Linux Kernel NFC LLCP implementation allows local users to escalate privileges through crafted socket operations. In llcp_sock_connect(), failure branches retain the reference returned by nfc_llcp_local_get() because they omit nfc_llcp_local_put(), leaking a local object reference. Exploitation requires low-privileged local code and a reachable NFC LLCP stack; Canonical documents memory exhaustion as the concrete denial-of-service outcome.
Summary
What happened
Use-after-free in the Linux Kernel NFC LLCP implementation allows local users to escalate privileges through crafted socket operations. In llcp_sock_connect(), failure branches retain the reference returned by nfc_llcp_local_get() because they omit nfc_llcp_local_put(), leaking a local object reference. Exploitation requires low-privileged local code and a reachable NFC LLCP stack; Canonical documents memory exhaustion as the concrete denial-of-service outcome.
The record
- CVE
- CVE-2020-25671
- Published
- May 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- 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?
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