Back

MEDIUM

Bluetooth: MGMT: Fix memory leak in set_ssp_complete

Published Feb 14, 2026

Description

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

Affected products

Remediation

Red Hat statement

A memory leak in the Bluetooth MGMT command completion path occurs because mgmt_pending_cmd objects are removed from the pending list but are not freed in both the success and error paths of set_ssp_complete. This results in leaked pending command structures and their associated parameter buffers for each completed SSP command. The same pattern also affects set_advertising_complete. Over time, repeated management operations can cause unbounded kernel memory growth and lead to resource exhaustion or degraded system stability. For the CVSS the PR:L choice is appropriate because triggering these completions typically requires access to Bluetooth management interfaces, which is commonly restricted to privileged users or processes with elevated capabilities. The primary impact is availability through memory pressure.

Weaknesses (2)

References (10)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner Linux
Published Feb 14, 2026
Updated May 23, 2026
Reserved Jan 13, 2026
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Moderate
Public date Feb 14, 2026
ENISA EUVD
Assigner Linux
Published Feb 14, 2026
Updated May 23, 2026
Exploited since n/a
EUVD-2026-5889