Local denial of service via NULL dereference
Published Aug 8, 2021 · Updated Aug 4, 2024
Linux kernel before 5.12.10 allows local unprivileged users to cause denial of service via a failed NFC LLCP bind followed by getsockname. In net/nfc/llcp_sock.c, a failed bind can leave service_name NULL, while llcp_sock_getname copies from that pointer without checking it, triggering a kernel NULL-pointer dereference and BUG. The attack requires local unprivileged access and NFC LLCP socket support; successful exploitation can panic or otherwise interrupt the kernel, with no stated confidentiality or integrity impact.
Summary
What happened
Linux kernel before 5.12.10 allows local unprivileged users to cause denial of service via a failed NFC LLCP bind followed by getsockname. In net/nfc/llcp_sock.c, a failed bind can leave service_name NULL, while llcp_sock_getname copies from that pointer without checking it, triggering a kernel NULL-pointer dereference and BUG. The attack requires local unprivileged access and NFC LLCP socket support; successful exploitation can panic or otherwise interrupt the kernel, with no stated confidentiality or integrity impact.
The record
- CVE
- CVE-2021-38208
- Published
- Aug 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 8, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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