dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-24512

MEDIUM · 5.6 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 →
58/100
Remediation priority · Elevated
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
Improper input validation 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. Authorized adversary with an authenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present with 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 (low) 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

Intel PROSet/Wireless WiFi Software driver before version 23.160 contains an improper input validation vulnerability that allows an authenticated local attacker with high complexity and special internal knowledge to cause a denial of service via the driver component (Ring 2).

MitigationUpdate Intel PROSet/Wireless WiFi Software to version 23.160 or later. In enterprise environments, test driver compatibility before broad deployment.

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

CVSS:3.1/AV:L/AC:H/PR:L/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 PROSet/Wireless WiFi Software is installed
    Check Windows installed programs list or registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Intel PROSet' or 'Wireless WiFi'
    Affected if The software is not found in the system, the vulnerability does not apply
  2. Locate the driver version
    Open Device Manager, expand Network adapters, find the Intel wireless adapter, check Driver Version property. Alternatively, run 'wmic path win32_pnpsigneddriver' and filter for Intel wireless drivers to get DriverVersion
    Affected if Unable to retrieve driver information indicates the Intel wireless driver may not be present
  3. Compare installed version to 23.160
    Identify the full version string (e.g., 23.160.0 or 23.100.0) from the driver properties or Intel PROSet installation. Compare numerically - any version earlier than 23.160 is in the affected range
    Affected if Installed version is a release before 23.160 (for example, 23.100.x, 22.x.x, or 21.x.x)
  4. Confirm the driver component is active
    Verify the wireless adapter is enabled and loaded by checking Device Manager status shows 'This device is working properly' or running 'netsh wlan show interfaces' to confirm the Intel WiFi adapter is active
    Affected if The driver is loaded and active; however, the vulnerability requires local authenticated access, so even if the driver is present but no local attacker with special knowledge exists, the practical risk differs

If Intel PROSet/Wireless WiFi Software is installed and the driver version is below 23.160, the system is affected by this vulnerability.

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. In enterprise environments, test driver compatibility before broad deployment.

Recommended fix Moderate confidence

Intel(R) PROSet/Wireless WiFi Software version 23.160 or later for Windows

  1. Navigate to the Intel website and download Intel(R) PROSet/Wireless WiFi Software version 23.160 or later
  2. Verify the downloaded version matches or exceeds 23.160
  3. Back up current wireless configuration settings if possible
  4. Install the updated WiFi software following Intel's standard installation procedures
  5. Restart the system to ensure the new driver loads properly
  6. Confirm the installed version is 23.160 or later via the software interface or Device Manager

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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