Local denial of service via failed LLCP connections
Published May 25, 2021 · Updated Aug 4, 2024
Memory leak in the Linux kernel NFC LLCP implementation allows local users to exhaust memory through repeated failed connections. In llcp_sock_connect(), kmemdup allocates service_name, but the sock_unlink error path returns without freeing it when nfc_llcp_send_connect() fails. Exploitation requires local execution and a usable NFC LLCP socket; repeated failures consume kernel memory and can interrupt the host.
Summary
What happened
Memory leak in the Linux kernel NFC LLCP implementation allows local users to exhaust memory through repeated failed connections. In llcp_sock_connect(), kmemdup allocates service_name, but the sock_unlink error path returns without freeing it when nfc_llcp_send_connect() fails. Exploitation requires local execution and a usable NFC LLCP socket; repeated failures consume kernel memory and can interrupt the host.
The record
- CVE
- CVE-2020-25672
- Published
- May 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 25, 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.
Weakness, pattern, technique
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