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

CVE-2025-30255

HIGH · 8.2 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 →
87/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 (low) 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

A vulnerability in Intel(R) PROSet/Wireless WiFi Software for Windows (versions before 23.160) contains an out-of-bounds write in the kernel-mode device driver (Ring 2) that can be exploited by an unauthenticated attacker via adjacent network access to cause denial of service.

MitigationUpdate Intel PROSet/Wireless WiFi Software to version 23.160 or later. Deploy through enterprise patch management tools and verify wireless connectivity post-update.

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
Low
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/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. Check Intel PROSet/Wireless WiFi Software version via Windows Registry
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Intel\PromWin, or use command: reg query "HKLM\SOFTWARE\Intel\PromWin" /v Version
    Affected if The version value is empty or shows a version lower than 23.160
  2. Check wireless adapter driver version in Device Manager
    Open Device Manager, expand Network adapters, right-click the Intel wireless adapter, select Properties, view the Driver version field
    Affected if The driver version corresponds to an Intel PROSet/Wireless version lower than 23.160
  3. Confirm wireless network adapter is present and enabled
    In Device Manager, verify that an Intel wireless network adapter exists under Network adapters and is not disabled
    Affected if An Intel wireless adapter is present and enabled, and its driver/proset version is below 23.160
  4. Verify the kernel-mode wireless driver is loaded
    Open Command Prompt and run: sc query iwdbg or check Device Manager driver status for the wireless adapter shows as 'Running'
    Affected if The Intel wireless driver (kernel-mode Ring 2 driver) is loaded and the software version is before 23.160

A user is affected if Intel PROSet/Wireless WiFi Software version is present and is lower than 23.160, with an active Intel wireless adapter driver loaded.

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. Deploy through enterprise patch management tools and verify wireless connectivity post-update.

Recommended fix High confidence

Intel PROSet/Wireless WiFi Software version 23.160 or later

  1. 1. Identify the current version of Intel(R) PROSet/Wireless WiFi Software installed on the system via Device Manager or the Intel PROSet control panel.
  2. 2. Navigate to Intel's official support website and locate the download page for Intel PROSet/Wireless WiFi Software.
  3. 3. Download version 23.160 or a later stable release of Intel PROSet/Wireless WiFi Software compatible with your Windows system.
  4. 4. Disable any antivirus or security software temporarily if required during installation.
  5. 5. Run the Intel PROSet/Wireless WiFi Software installer with administrator privileges.
  6. 6. Follow the on-screen installation prompts and restart the system when prompted to complete the update.
  7. 7. After rebooting, verify the installed version matches or exceeds 23.160 via Device Manager or the Intel utility.
Caveat Review Intel release notes for version 23.160 for any changes to supported hardware or configuration requirements before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30255 — 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-30255 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