bluetooth vulnerability

CVE-2026-68189 is a newly published Linux-kernel Bluetooth flaw tied to a race in the hci_sync code’s traversal of a UUID list, and it does not affect the Windows 10, Windows 11, or Windows Server Bluetooth stack. The practical action for most WindowsForum readers is therefore none: there is no...

A dealer-installed anti-theft system meant to make cars harder to steal has instead created a Bluetooth security problem affecting an estimated 2.2 million vehicles—and the most urgent step for owners is to apply the newly released firmware update. Researchers at the University of California San...

CVE-2026-42975, a heap-based buffer overflow in the Windows Bluetooth Port Driver, can let an unauthenticated attacker execute code by reaching a vulnerable PC over an adjacent network. Microsoft fixed the high-severity flaw in its July 14, 2026 security updates, making prompt installation the...

Google Chrome for Windows versions before 150.0.7871.47 are affected by CVE-2026-14119, a Bluetooth type-confusion flaw disclosed on June 30, 2026, that can let a nearby attacker using a malicious peripheral read potentially sensitive memory from a Chrome process. The bug is not a...

CVE-2026-13035 is a high-severity use-after-free vulnerability in Google Chrome’s Bluetooth code on macOS, disclosed June 24, 2026, and fixed for Mac users in Chrome 149.0.7827.197 after Google’s Stable Channel desktop update. The short version is simple: if Chrome on a Mac is older than that...

Google Chrome CVE-2026-11699 is a high-severity use-after-free vulnerability in Chrome’s Bluetooth code on macOS, disclosed in June 2026 and fixed for Mac users in Chrome 149.0.7827.103 after Google’s stable-channel desktop security update. The bug is not the loudest Chrome flaw of the month...

CVE-2026-46056 is a newly published Linux kernel Bluetooth vulnerability, disclosed by kernel.org and added to NVD on May 27, 2026, involving a potential use-after-free in Secure Simple Pairing passkey event handlers. The fix is small, but the lesson is not: Bluetooth remains one of the kernel’s...

A newly cataloged Windows vulnerability, tracked as CVE-2025-59513, affects the Bluetooth RFCOM protocol driver and is described by Microsoft as an information‑disclosure flaw that can allow a local, unauthorized actor to obtain sensitive kernel or driver memory when interacting with the RFCOM...

A use-after-free flaw in the Windows Bluetooth Service has been cataloged as CVE-2025-58728 and classified as a local elevation-of-privilege vulnerability that Microsoft patched as part of the October 2025 update cycle; the weakness can allow an authenticated, local user process to corrupt...

A newly cataloged vulnerability, CVE-2025-59290, affects the Windows Bluetooth Service and is described by vendors and trackers as a use‑after‑free (UAF) memory‑corruption flaw that allows an authorized local attacker to elevate privileges on an affected host. A patch was published on October...

On October 8, 2024, Microsoft made an update concerning CVE-2021-1638, which pertains to a Bluetooth security feature bypass vulnerability. This vulnerability has been a point of interest for Windows users, especially those concerned about the security implications of Bluetooth technology within...

Introduction Mark your calendars: October 8, 2024, just marked a moment of change for those keeping an eye on the ever-evolving landscape of cybersecurity. A seemingly simple update has been issued concerning CVE-2021-1684, a vulnerability affecting Windows Bluetooth features, particularly its...

On August 13, 2024, Microsoft disclosed a significant vulnerability in its Windows Bluetooth driver known as CVE-2024-38123. This vulnerability poses an information disclosure risk, potentially allowing attackers to obtain sensitive information through Bluetooth connections. Understanding this...

:eek: