CVE-2026-40695: Intel Wireless Bluetooth null pointer dereference denial of service

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

Intel Wireless Bluetooth drivers contain a null pointer dereference vulnerability in kernel-mode code that can cause a system crash or denial of service. An authenticated local attacker can trigger this condition with low complexity, causing the system to become unavailable without requiring user interaction.

Technologies: Intel Wireless Bluetooth. Vendors: Intel.

Quick answers

Is CVE-2026-40695 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-40695 being exploited in the wild.
How severe is CVE-2026-40695?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Intel Wireless Bluetooth.
Is there a fix for CVE-2026-40695?
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-40695 attacked?
It is attacked with local access, in device firmware.
Am I affected by CVE-2026-40695?
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 null pointer dereference in Intel Wireless Bluetooth kernel-mode (Ring 0) driver code allows an authenticated local attacker to trigger a denial of service. The vulnerability requires low attack complexity and no additional privileges or user interaction, accessed via local means without special preconditions.

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.