Process crash via P2P peer use-after-free
Published Feb 26, 2021 · Updated Dec 18, 2025
Use-after-free in wpa_supplicant 1.0 through 2.9 allows physically proximate attackers to crash the process via crafted P2P frames. An invalid Provision Discovery Request can evict the oldest peer entry while processing continues to read and write the freed allocation. Exploitation requires CONFIG_P2P and active P2P discovery within radio range; process termination is confirmed, while code execution remains potential.
Summary
What happened
Use-after-free in wpa_supplicant 1.0 through 2.9 allows physically proximate attackers to crash the process via crafted P2P frames. An invalid Provision Discovery Request can evict the oldest peer entry while processing continues to read and write the freed allocation. Exploitation requires CONFIG_P2P and active P2P discovery within radio range; process termination is confirmed, while code execution remains potential.
The record
- CVE
- CVE-2021-27803
- Published
- Feb 26, 2021
- Updated
- Dec 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2021CVE publishedPublication date reported by the CVE source.
- Dec 18, 2025Record 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.
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