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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 24.50
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 24.50.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 7/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
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
Read the source excerpt
“Intel® Wireless Bluetooth® before version 24.50 (integrated Wireless products)”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 24.50.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- n/a Intel(R) Wireless Bluetooth(R)
Version range not reported
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-42956
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: cve.now feed data
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: intel.com
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: intel.com
How do I fix CVE-2026-42956?
Intel recommends updating Intel PROSet/Wireless Wi-Fi software to version 24.50 or later.Source: intel.com