BlueBorne Linux Kernel L2CAP Stack Buffer Overflow
CVE-2017-1000251 is a stack-based buffer overflow in the Linux kernel's native Bluetooth stack, affecting versions 2.6.32 through 4.13.1 inclusive, unless vendor fixes have been backported. Improper processing of crafted L2CAP configuration responses allows a nearby attacker to corrupt kernel stack memory and potentially execute arbitrary code in kernel space. The vulnerability is part of the BlueBorne vulnerability family disclosed in September 2017.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise the affected system through arbitrary code execution with kernel privileges, enabling unauthorized access to data, modification of system state, and interference with security controls. Memory corruption can also cause kernel crashes and denial of service.
If you can’t patch tonight, do this now.
Disable Bluetooth on affected systems until a patched kernel can be deployed. Keep Bluetooth disabled where it is unnecessary. Pairing restrictions alone should not be treated as protection against BlueBorne attacks.
Patch, then assume compromise.
Install the operating-system or device vendor's kernel update addressing CVE-2017-1000251, or migrate to a supported kernel release containing the fix. Reboot into the patched kernel and verify the running kernel's patch status. A userspace BlueZ update alone does not address this kernel vulnerability.
3 exploits validated by Mallory's analysis. Hidden: 2 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.