linux-cve-announce - CVE-2026-23151: Bluetooth: MGMT: Fix memory leak in set_ssp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2026021414-CVE-2026-23151-74d4@gregkh>
Date: Sat, 14 Feb 2026 17:04:17 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23151: Bluetooth: MGMT: Fix memory leak in set_ssp_complete

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

The Linux kernel CVE team has assigned CVE-2026-23151 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 6.12.59 with commit d71b98f253b079cbadc83266383f26fe7e9e103b and fixed in 6.12.69 with commit 1850a558d116d7e3e2ef36d06a56f59b640cc214
	Issue introduced in 6.17 with commit 302a1f674c00dd5581ab8e493ef44767c5101aab and fixed in 6.18.9 with commit 3b6318505378828ee415d6ef678db6a74c077504
	Issue introduced in 6.17 with commit 302a1f674c00dd5581ab8e493ef44767c5101aab and fixed in 6.19 with commit 1b9c17fd0a7fdcbe69ec5d6fe8e50bc5ed7f01f2
	Issue introduced in 6.16.10 with commit 87a1f16f07c6c43771754075e08f45b41d237421

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-23151
will be updated if fixes are backported, please check that for the most
up to date information about this issue.

Affected files
==============

The file(s) affected by this issue are:
	net/bluetooth/mgmt.c

Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/1850a558d116d7e3e2ef36d06a56f59b640cc214
	https://git.kernel.org/stable/c/3b6318505378828ee415d6ef678db6a74c077504
	https://git.kernel.org/stable/c/1b9c17fd0a7fdcbe69ec5d6fe8e50bc5ed7f01f2