Daemon crash via double-free during P2P parsing
Published Mar 3, 2024 · Updated Nov 4, 2025
Improper initialization in p2putil.c in IWD 2.15 and earlier allows remote attackers to crash the wireless daemon. When advertised-service parsing fails after allocating descriptors, the error path destroys the queue but leaves its pointer non-null, causing later cleanup to destroy it again. Exposure requires the daemon to parse malformed advertised-service information received through Wi-Fi P2P; the reported consequence is a daemon crash.
Summary
What happened
Improper initialization in p2putil.c in IWD 2.15 and earlier allows remote attackers to crash the wireless daemon. When advertised-service parsing fails after allocating descriptors, the error path destroys the queue but leaves its pointer non-null, causing later cleanup to destroy it again. Exposure requires the daemon to parse malformed advertised-service information received through Wi-Fi P2P; the reported consequence is a daemon crash.
The record
- CVE
- CVE-2024-28084
- Published
- Mar 3, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-665, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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