Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2017-1000251: BlueBorne Linux Kernel L2CAP Stack Buffer Overflow

Published Sep 12, 2017 · Updated 28 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.0High · v3.1
EPSS16.2%97th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
Debian ProjectRed HatNVIDIA CorporationLinux
IdentifiersCVE-2017-1000251CWE-121

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
Blue-BorneThis repository provides operational proof-of-concept exploits for the BlueBorne Bluetooth vulnerabilities, specifically targeting Android devices (CVE-2017-0781 for RCE and CVE-2017-0785 for information leak/ASLR bypass). The main exploit is implemented in 'android/doit.py', which orchestrates the attack by first leaking memory addresses via SDP (Service Discovery Protocol) to bypass ASLR, then exploiting a heap overflow in the Bluetooth stack to achieve remote code execution. The payload is a reverse shell, implemented as a shell command using toybox nc, which connects back to the attacker's machine. The exploit requires a compatible Bluetooth adapter (CSR), specific vulnerable Android versions, and network accessibility for the reverse shell. The repository also includes a general L2CAP testing framework under 'l2cap_infra', which is used for low-level Bluetooth protocol manipulation and testing. No hardcoded IP addresses or domains are present, but the exploit targets specific system libraries for version-dependent offsets. The code is mature and functional, but not weaponized for mass exploitation.CrackSoft900 · Disclosed Oct 12, 2020 · python · bluetoothOperationalBlueborne-CVE-2017-1000251This repository provides a proof-of-concept (PoC) exploit for the BlueBorne vulnerability (CVE-2017-1000251), which affects the Linux BlueZ Bluetooth stack. The main exploit file, 'bluebornexploit.py', uses the Scapy library to craft and send malformed L2CAP configuration packets to a target Bluetooth device, specified by its MAC address. The exploit aims to trigger a Denial of Service (DoS) by exploiting improper handling of L2CAP configuration requests and responses. The 'bluetoothsrv.py' file appears to be a simple Bluetooth L2CAP server for testing purposes. The repository is structured with a README describing its purpose, the main exploit script, and a test server script. No network endpoints such as URLs or IPs are present; instead, Bluetooth MAC addresses are used as targets. The exploit requires proximity to the target and a Bluetooth adapter capable of raw packet injection.hayzamjs · Disclosed Sep 23, 2017 · python · bluetoothPoCblueborne-CVE-2017-1000251This repository contains a proof-of-concept (PoC) exploit for the BlueBorne Bluetooth vulnerability (CVE-2017-1000251) affecting Linux kernels prior to 4.13.1. The main exploit code is in 'blueborne.c', which crafts and sends a series of malicious L2CAP packets over a raw Bluetooth socket to a specified target Bluetooth MAC address. The exploit is designed to trigger a buffer overflow in the kernel's Bluetooth stack, resulting in a denial of service (kernel panic/crash) on the target system. The exploit does not provide remote code execution or a shell; it is strictly a DoS PoC. The repository also includes a README describing the exploit, a text file ('blueborne.txt') with additional protocol details and usage notes, and a kernel call trace log ('dmesg_call-trace.txt') showing the crash. The exploit requires the attacker to know the target's Bluetooth MAC address and to be within Bluetooth range. No network, HTTP, or file-based endpoints are present; the only fingerprintable endpoint is the target's Bluetooth MAC address.sgxgsx · Disclosed Jul 3, 2024 · c · bluetoothPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
LinuxLinux Kerneloperating_system
NVIDIA CorporationJetson Tk1hardware
NVIDIA CorporationJetson Tx1hardware
Red HatEnterprise Linux Desktopoperating_system
Red HatEnterprise Linux Serveroperating_system
Red HatEnterprise Linux Server Ausoperating_system
Red HatEnterprise Linux Server Eusoperating_system
Red HatEnterprise Linux Server Tusoperating_system
Red HatEnterprise Linux Workstationoperating_system
FAQ

Frequently asked questions

Is CVE-2017-1000251 exploited in the wild?
As of Oct 25, 2026, Mallory has no reports of CVE-2017-1000251 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-1000251?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2017-1000251, the earliest disclosed Sep 23, 2017.
Is there a patch for CVE-2017-1000251?
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.
What products are affected by CVE-2017-1000251?
Linux Kernel, Debian Project Debian Linux, Red Hat Enterprise Linux Desktop, Red Hat Enterprise Linux Server, Red Hat Enterprise Linux Server Aus, and 5 more.
How severe is CVE-2017-1000251?
CVE-2017-1000251 has a CVSS v3.1 score of 8.0 (High) and an EPSS score of 16.2% (97th percentile) as of Oct 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.