Adjacent service interruption via use-after-free
Published Feb 12, 2025 · Updated Feb 18, 2025
Use-after-free in Intel PROSet/Wireless WiFi and Killer WiFi software before 23.80 allows physically proximate attackers to interrupt service. Intel identifies a use-after-free condition but does not disclose the affected routine, freed object, or input sequence that reuses it. Adjacent wireless access is required; no authentication or user interaction is needed, and Intel does not specify whether the failure is a hang, crash, or reboot.
Summary
What happened
Use-after-free in Intel PROSet/Wireless WiFi and Killer WiFi software before 23.80 allows physically proximate attackers to interrupt service. Intel identifies a use-after-free condition but does not disclose the affected routine, freed object, or input sequence that reuses it. Adjacent wireless access is required; no authentication or user interaction is needed, and Intel does not specify whether the failure is a hang, crash, or reboot.
The record
- CVE
- CVE-2024-41168
- Published
- Feb 12, 2025
- Updated
- Feb 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 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.
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