dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-33029

HIGH · 7.4 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Out-of-bounds write for some Intel(R) PROSet/Wireless WiFi Software for Windows before version 23.160 within Ring 2: Device Drivers may allow a denial of service. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via adjacent access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (high) impacts.

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 · high confidence

Out-of-bounds write vulnerability in Intel PROSet/Wireless WiFi device drivers for Windows (Ring 2/kernel mode). An unauthenticated, unprivileged attacker with adjacent network access can trigger an out-of-bounds memory write in the WiFi driver, causing a denial of service. The attack requires low complexity and no user interaction.

MitigationUpdate Intel PROSet/Wireless WiFi Software to version 23.160 or later. No workarounds available for driver-level kernel vulnerabilities; disabling the wireless adapter would prevent exploitation but also eliminate connectivity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Intel wireless adapter is present
    Open Device Manager, expand 'Network adapters', and look for Intel WiFi adapters (e.g., Intel Wi-Fi 6 AX200, AX201, etc.) OR run 'Get-NetAdapter -Physical | Where-Object {$_.InterfaceDescription -like "*Intel*"}' in PowerShell
    Affected if No Intel wireless adapter found means the system is not affected by this specific WiFi driver vulnerability
  2. Check Intel PROSet/Wireless WiFi Software version
    Check the installed version via Control Panel > Programs and Features, look for 'Intel PROSet/Wireless WiFi Software' or 'Intel Wireless Bluetooth', OR check registry key 'HKLM\SOFTWARE\Intel\Ndis\CurrentVersion' if accessible
    Affected if Version is present and is below 23.160 (e.g., 23.130, 22.x, 21.x series)
  3. Check the WiFi driver version
    In Device Manager, right-click the Intel WiFi adapter, select 'Properties' > 'Driver' tab, note the driver version OR run 'driverquery /v | findstr /i "intel.*wifi"' in command prompt
    Affected if Driver version corresponds to PROSet/Wireless Software versions before 23.160; driver file dates earlier than the 23.160 release timeframe
  4. Confirm wireless adapter is enabled
    Run 'Get-NetAdapter | Where-Object {$_.Status -eq "Up"}' in PowerShell or check Network & Internet settings in Windows
    Affected if Wireless adapter is enabled and actively running; if disabled, the vulnerability cannot be exploited though the vulnerable software may still be present

System is affected if it has an Intel WiFi adapter with Intel PROSet/Wireless WiFi Software installed at a version earlier than 23.160, with the wireless adapter enabled and accessible to adjacent attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Intel PROSet/Wireless WiFi Software to version 23.160 or later. No workarounds available for driver-level kernel vulnerabilities; disabling the wireless adapter would prevent exploitation but also eliminate connectivity.

Recommended fix High confidence

Intel PROSet/Wireless WiFi Software version 23.160 or later

  1. Identify the current version of Intel PROSet/Wireless WiFi Software installed on the system via Device Manager or the Intel Driver & Support Assistant
  2. Navigate to Intel's official support website or use Intel Driver & Support Assistant to check for updates
  3. Download Intel PROSet/Wireless WiFi Software version 23.160 or later for your specific wireless adapter model
  4. Run the installer and follow the on-screen instructions to update the wireless software
  5. Restart the computer to complete the driver installation
Caveat Minor: Wireless connectivity may be briefly interrupted during driver update; ensure backup connectivity is available if the system requires network access

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33029 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33029 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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