Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23151

Bluetooth: MGMT: Fix memory leak in set_ssp_complete

Description

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().

Timeline

  1. ID reserved

    By Linux

  2. · 32 days later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23151, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a – < d7e42dc47beb48851bc0008c1e1b79126de9d975
    • affected d71b98f253b079cbadc83266383f26fe7e9e103b – < 1850a558d116d7e3e2ef36d06a56f59b640cc214
    • affected 302a1f674c00dd5581ab8e493ef44767c5101aab – < 3b6318505378828ee415d6ef678db6a74c077504
    • affected 302a1f674c00dd5581ab8e493ef44767c5101aab – < 1b9c17fd0a7fdcbe69ec5d6fe8e50bc5ed7f01f2
    • affected 87a1f16f07c6c43771754075e08f45b41d237421
    • affected 6.12.59 – < 6.12.69
    • affected 6.16.10 – < 6.17
  • Linux · Linux

    • affected 6.17
    • unaffected < 6.17
    • unaffected 6.12.69 – ≤ 6.12.*
    • unaffected 6.18.9 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23151 badge
[![CVE-2026-23151](https://cveledger.app/badge/CVE-2026-23151.svg)](https://cveledger.app/cve/CVE-2026-23151)

Record last updated .