dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-35967

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 read 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 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

An out-of-bounds read vulnerability exists in Intel PROSet/Wireless WiFi Software for Windows versions before 23.160 within the device driver (Ring 2). An unauthenticated, unprivileged attacker with adjacent network access can exploit this low-complexity, no-interaction flaw to cause a denial of service.

MitigationUpgrade Intel PROSet/Wireless WiFi Software to version 23.160 or later to address the vulnerability.

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. Check if Intel PROSet/Wireless WiFi Software is installed
    Open Windows Settings > Apps > Apps & features and search for 'Intel PROSet' or 'Intel Wireless' in the installed programs list, or check Device Manager under Network adapters for an Intel wireless device
    Affected if The software or Intel wireless hardware drivers are present on the system
  2. Locate the Intel wireless driver version
    Open Device Manager, expand Network adapters, right-click on the Intel wireless adapter, select Properties, go to the Driver tab, and note the Driver Version field
    Affected if The driver version shown is older than the version bundled with Intel PROSet 23.160
  3. Find the Intel PROSet/Wireless version via registry
    Open Registry Editor and navigate to HKLM\SOFTWARE\Intel\Proset\Wireless or HKLM\SOFTWARE\WOW6432Node\Intel\Proset\Wireless, then check the Version or VersionEx value in the right pane
    Affected if The version value is present and is less than 23.160 (for example, 23.130, 22.x, or earlier)
  4. Check the wireless driver file version
    Locate the driver files in the Windows System32\DriverStore\FileRepository folder (or via Driver Details in Device Manager), and right-click the main .sys driver file (such as 'Netwtw02.sys' or similar Intel wireless driver) to view its File Version property
    Affected if The driver file version is older than what ships with PROSet 23.160

The system is affected if Intel PROSet/Wireless WiFi Software or its associated wireless driver version is installed and is lower than version 23.160.

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

Upgrade Intel PROSet/Wireless WiFi Software to version 23.160 or later to address the vulnerability.

Recommended fix Moderate confidence

Intel PROSet/Wireless WiFi Software version 23.160 or later

  1. Navigate to the official Intel Support website or Intel Driver & Support Assistant
  2. Locate Intel(R) PROSet/Wireless WiFi Software for Windows
  3. Download version 23.160 or later
  4. Run the installer as administrator
  5. Follow the on-screen installation prompts
  6. Restart the system to complete the driver update

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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