LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23151: Bluetooth: MGMT: Fix memory leak in set_ssp_complete

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix memory leak in set_ssp_complete Fix memory leak in set_ssp_complete() where mgmt_pending_cmd structures are not freed after being removed from the pending list. Commit 302a1f674c00 ("Bluetooth: MGMT: Fix possible UAFs") replaced mgmt_pending_foreach() calls with individual command handling but missed adding mgmt_pending_free() calls in both error and success paths of set_ssp_complete(). Other completion functions like set_le_complete() were fixed correctly in the same commit. This causes a memory leak of the mgmt_pending_cmd structure and its associated parameter data for each SSP command that completes. Add the missing mgmt_pending_free(cmd) calls in both code paths to fix the memory leak. Also fix the same issue in set_advertising_complete().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue leaks a small Bluetooth management command object each time certain Bluetooth settings commands complete. Over time, repeated triggering could waste kernel memory. The public record does not provide CVSS, a confirmed attacker path, or evidence of active exploitation.

Executive priority

Handle through standard kernel patch management, with higher priority for fleets where Bluetooth is enabled or user-accessible. Current evidence supports maintenance urgency, not emergency response, because severity and exploitation evidence are not provided.

Technical view

The bug is a missing mgmt_pending_free(cmd) after pending commands are removed in set_ssp_complete(), with the same issue fixed in set_advertising_complete(). It followed commit 302a1f674c00, which changed pending command handling and omitted frees on success and error paths.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions with Bluetooth management functionality present. The source lists Linux kernel affected versions including 6.17, 6.12.69, 6.18.9, and 6.19, but does not map this cleanly to distributions or appliances.

Exploitation context

No KEV listing is present, and the supplied sources do not report active exploitation or public exploit details. The practical risk depends on whether an attacker can repeatedly cause relevant Bluetooth management SSP or advertising commands to complete on the target system.

Researcher notes

The record identifies a kernel memory leak in Bluetooth MGMT completion paths. It does not provide CVSS, CWE, exploitability analysis, prerequisites, or distro-specific fixed package versions. Avoid assuming remote exploitability from Bluetooth involvement alone.

Mitigation direction

  • Check your Linux distribution kernel advisory for CVE-2026-23151 status.
  • Update to a kernel build containing the referenced stable fixes.
  • Prioritize Bluetooth-enabled hosts, kiosks, laptops, and shared Linux systems.
  • Disable Bluetooth where it is not operationally required.
  • Monitor vendor advisories for CVSS and backport details.

Validation and detection

  • Inventory Linux kernel versions across managed systems.
  • Identify systems with Bluetooth enabled or loaded Bluetooth kernel modules.
  • Confirm whether vendor kernel packages include the stable fix commits.
  • Review kernel logs and memory trends on Bluetooth-enabled systems.
  • Track remediation through distribution package metadata, not upstream version numbers alone.
Prepared
Confidence
medium
Sources
6

Public sources used

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.

cve · low confidence lookup

CVE-2026-23151 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
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a, d71b98f253b079cbadc83266383f26fe7e9e103b, 302a1f674c00dd5581ab8e493ef44767c5101aab, 302a1f674c00dd5581ab8e493ef44767c5101aab, 87a1f16f07c6c43771754075e08f45b41d237421, 6.12.59, 6.16.10unaffected
LinuxLinux6.17, 0, 6.12.69, 6.18.9, 6.19affected
Weakness

CWE details

No CWE listed

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