CVE-2025-20046
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse after free for some Intel(R) PROSet/Wireless WiFi Software for Windows before version 23.100 may allow an unauthenticated user to potentially enable denial of service via adjacent access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA use-after-free vulnerability exists in Intel PROSet/Wireless WiFi Software for Windows versions prior to 23.100. An unauthenticated attacker with adjacent network access can exploit this memory corruption flaw to cause a denial of service condition.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 23.100.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Intel PROSet/Wireless WiFi Software is installedOpen Windows Settings > Apps & Features and search for 'Intel PROSet' or 'Intel Wireless' in the installed programs list. Alternatively, open Device Manager, expand Network adapters, and look for an Intel wireless adapter.Affected if Intel PROSet/Wireless WiFi Software is not present on the system - not affected
-
Find the installed version of Intel PROSet/Wireless WiFi SoftwareIn Settings > Apps & Features, locate Intel PROSet/Wireless WiFi Software and note the version number shown in the version column. If not visible there, right-click the Intel wireless adapter in Device Manager, select Properties, go to the Driver tab, and record the Driver Version.Affected if Cannot determine version - verify manually through Intel driver download page or system information tools
-
Compare installed version to affected rangeTake the version number found in the previous step and compare it numerically against version 23.100.0. Any version lower than 23.100.0 (such as 23.90, 23.80, 22.x, 21.x) falls within the affected range.Affected if Installed version is 23.100.0 or higher - not affected; version is below 23.100.0 - affected
-
Confirm WiFi functionality is activeCheck if the Intel wireless adapter is enabled and the system has WiFi capability active. Look for the WiFi icon in the system tray or check Settings > Network & Internet > WiFi to see if WiFi is turned on.Affected if WiFi adapter is disabled or not in use - vulnerability cannot be triggered even with affected version
A system is affected by this CVE when Intel PROSet/Wireless WiFi Software version is below 23.100.0 AND the WiFi adapter is enabled and operational.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.100.0
Upgrade Intel PROSet/Wireless WiFi Software to version 23.100 or later to remediate this vulnerability.
Intel PROSet/Wireless WiFi Software version 23.100.0 or later
- Identify the current version of Intel(R) PROSet/Wireless WiFi Software installed on the system via Windows Device Manager or the Intel PROSet software interface
- Navigate to the official Intel support website and locate the Intel PROSet/Wireless WiFi Software download page
- Download version 23.100.0 or later of Intel PROSet/Wireless WiFi Software for Windows
- Run the installer and follow the on-screen prompts to update the software
- Restart the computer if prompted to complete the installation
- Verify the installed version matches or exceeds 23.100.0 via the software interface or Device Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20046 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data