CVE-2026-24911 is a stack-based buffer overflow in Intel PROSet/Wireless Wi-Fi software for Windows, running in kernel mode (Ring 0). The record scores it 8.6 (High) and says it can cause denial of service. Intel's advisory INTEL-SA-01468 says to update the Wi-Fi software to version 24.30 or later.
What's affected
Intel's advisory INTEL-SA-01468 covers CVE-2026-22887 and CVE-2026-24911 together. It lists Intel Wi-Fi 6, 6E and 7 adapters (AX201, AX210, AX211, BE200, BE201, BE211, BE213) and their Killer variants, plus the older Wireless-AC 9461, 9462 and 9560. Intel names Windows and Linux among the platforms. The fixed version is 24.30 or later.
Source conflict to note: the CVE record scores this 8.6 (High) with CVSS 3.1, and lists a narrower set of adapters such as Wi-Fi 6 AX200 and several Killer models. Intel's advisory rates both CVEs 8.3 (High) with CVSS 4.0 and lists the wider adapter set above. Use Intel's list for your inventory.
Weakness class: CWE-121.
How to check if you're exposed
On a Windows machine, open Device Manager, expand Network adapters, open the properties of the Intel Wi-Fi adapter, and read the Driver tab for the driver version. Intel's PROSet/Wireless software has its own version number, which you can read in Apps and features. You need 24.30 or later.
For a fleet, query your endpoint management tool for installed Intel Wi-Fi driver and PROSet versions and the adapter model. Adapters from the lists in the affected section are in scope. The Intel Driver and Support Assistant can also report outdated Intel drivers on a single machine.
What to do now
- Update Intel PROSet/Wireless Wi-Fi software to 24.30 or later from Intel's download center, or through your device maker's driver channel.
- Inventory Windows laptops by Wi-Fi adapter model and driver version, and update the oldest first.
- Check Linux machines with the listed adapters against Intel's advisory, since the page we read does not link a Linux download.
- Treat CVE-2026-22887 in the same change, because both CVEs share one advisory and one fix version.
- Add Wi-Fi driver version to your standard compliance report so kernel-mode drivers do not fall behind unnoticed.
Why it matters
Both bugs are memory safety faults in driver code that runs with the highest privilege on the machine. A buffer overflow in kernel mode can bring down the whole system. The record describes a stack buffer overflow in kernel mode driver code, with an adjacent attack vector and no privileges or user interaction needed.
The impact in the record is availability only. An attacker within wireless range could, in principle, crash the machine, which matters for kiosks, point of sale terminals and any laptop used during travel. Kernel crashes are also the first thing attackers learn about before trying for more. The KEV flag is false in the record, and Intel's advisory describes no exploitation.
Driver updates are easy to forget because they do not arrive through the usual application patch process. If your laptop fleet relies only on operating system updates, check whether Wi-Fi driver updates are actually reaching users.
Quick check
Is code execution possible?
Neither the record nor Intel's advisory claims it. Both describe denial of service, with high availability impact.
What if my adapter is not on the list?
Intel notes its product table may change. Re-read the advisory and confirm with your hardware vendor.
Sources
Last reviewed: 18 October 2026.
