LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1000251: The native Bluetooth stack in the Linux Kernel (BlueZ), starting at the Linux kernel version 2.6.32 and up...

The native Bluetooth stack in the Linux Kernel (BlueZ), starting at the Linux kernel version 2.6.32 and up to and including 4.13.1, are vulnerable to a stack overflow vulnerability in the processing of L2CAP configuration responses resulting in Remote code execution in kernel space.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a Bluetooth-related Linux kernel flaw from 2017. A nearby attacker could potentially trigger a stack overflow and run code in kernel space on affected systems. The bundle identifies Linux kernels 2.6.32 through 4.13.1 as affected. Business urgency is highest for older Linux devices where Bluetooth remains enabled. Exposure is most likely on legacy Linux systems, appliances, or embedded devices running kernels from 2.6.32 through 4.13.1 with Bluetooth enabled or reachable. Assets without Bluetooth hardware, disabled Bluetooth, or vendor-patched kernels are less likely to be exposed. Treat this as high priority for legacy or unmanaged Linux assets. Kernel-space remote code execution is serious, but exposure is narrower than internet-facing vulnerabilities because Bluetooth reachability is required. Confirm whether affected old kernels still exist before launching broad remediation. Mitigation focus: Apply relevant vendor kernel security updates for affected Linux distributions and devices.; Upgrade beyond affected kernel versions or to a vendor-fixed kernel build.; Disable Bluetooth on systems where it is not operationally required..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-1000251 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
18Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.