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

Published Feb 14, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: MGMT: Fix memory leak in setsspcomplete

Fix memory leak in setsspcomplete() where mgmtpendingcmd structures are not freed after being removed from the pending list.

Commit 302a1f674c00 ("Bluetooth: MGMT: Fix possible UAFs") replaced mgmtpendingforeach() calls with individual command handling but missed adding mgmtpendingfree() calls in both error and success paths of setsspcomplete(). Other completion functions like setlecomplete() were fixed correctly in the same commit.

This causes a memory leak of the mgmtpendingcmd structure and its associated parameter data for each SSP command that completes.

Add the missing mgmtpendingfree(cmd) calls in both code paths to fix the memory leak. Also fix the same issue in setadvertisingcomplete().

Affected Software

12 affected components
Linux Linux kernel
Linux Linux kernel>=6.12.59<6.12.69
Linux Linux kernel>=6.16.10<6.17
Linux Linux kernel>=6.17.1<6.18.9
Linux Linux kernel=6.17
Linux Linux kernel=6.19-rc1
Linux Linux kernel=6.19-rc2
Linux Linux kernel=6.19-rc3
Linux Linux kernel=6.19-rc4
Linux Linux kernel=6.19-rc5
Linux Linux kernel=6.19-rc6
Linux Linux kernel=6.19-rc7

Event History

Feb 14, 2026
CVE Published
via MITRE·04:01 PM
Data Sourced
via MITRE·04:01 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What access does an attacker need to exploit this issue?

The CVSS vector indicates local access and low privileges are required, with no user interaction. The impact is limited to availability through memory exhaustion; no confidentiality or integrity impact is indicated.

2

Which operations trigger the leak?

The leak occurs when SSP commands complete, because pending command structures and associated parameter data are not freed on either success or error paths. The same issue also affects completion of advertising operations in set_advertising_complete().

3

What can be done if patching cannot be applied immediately?

The provided data identifies a patch as available, but does not specify a configuration workaround. Reducing access for low-privileged local users may limit who can trigger the affected Bluetooth management operations.

4

How can administrators determine whether a system is affected?

Review the kernel source or applied stable commits for the missing mgmt_pending_free(cmd) calls in the success and error paths of set_ssp_complete() and in set_advertising_complete(). The referenced stable commits provide the available fixes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203