CERT-Bund flags Linux kernel Bluetooth flaws that let a local attacker cause DoS. Medium, local-only: patch on your normal cycle if the box has Bluetooth; headless servers without it can skip.Cyber Resilience desk
Sources (19)
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
- cert_bund · cert_bund
What this means for you — CISO:Apply the Linux kernel update on fleets where Bluetooth is present or enabled; prioritize endpoints and any host where local access is plausible. Hosts with Bluetooth disabled or absent can follow the normal patch cycle.
What this means for you — Lean IT orgs:If you use Linux laptops or desktops with Bluetooth on, install the kernel update through your usual updater. Machines without Bluetooth, or with it turned off, can wait for the regular update cycle.
What this means for you — MSP:Inventory client Linux systems with Bluetooth enabled and roll the kernel patch in your normal windows, endpoints first. Note any servers left with Bluetooth on for earlier attention.
What this means for you — Researcher:CERT-Bund WID-SEC-2026-1684 tracks multiple local Bluetooth DoS issues in the Linux kernel; use it and the upstream fixes for affected versions and CVE mapping.