CVE-2026-42056: Intel Wireless Bluetooth stack-based buffer overflow

CVE-2026-42056 · Severity: info · Published 2026-11-10

Intel Wireless Bluetooth firmware contains a stack-based buffer overflow in the kernel-mode driver that can crash the wireless subsystem. An attacker with adjacent network access can trigger a denial of service without authentication or user interaction, making the device's Bluetooth connectivity unavailable.

Technologies: Intel Wireless Bluetooth. Vendors: Intel.

Quick answers

Is CVE-2026-42056 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-42056 being exploited in the wild.
How severe is CVE-2026-42056?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Intel Wireless Bluetooth.
Is there a fix for CVE-2026-42056?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-42056 attacked?
It is attacked from the adjacent network or over the network, in device firmware.
Am I affected by CVE-2026-42056?
Check whether you run Intel Wireless Bluetooth. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A stack-based buffer overflow exists in Intel Wireless Bluetooth Ring 0 (kernel) code accessible via adjacent network attack vector. An unauthenticated attacker with low complexity attack requirements can trigger the overflow, resulting in denial of service to the Bluetooth subsystem. The vulnerability requires no user interaction or special privileges.

Affected products

  • Intel Wireless Bluetooth

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.