CVE-2026-43059: Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers

Severity: high (CVSS 7.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-05-05 · updated 2026-10-21
Weakness: CWE-416

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers Commit 302a1f674c00 ("Bluetooth: MGMT: Fix possible UAFs") introduced mgmt_pending_valid(), which not only validates the pending command but also unlinks it from the pending list if it is valid. This change in semantics requires updates to several completion handlers to avoid list corruption and memory safety issues. This patch addresses two left-over issues from the aforementioned rework: 1. In mgmt_add_adv_patterns_monitor_complete(), mgmt_pending_remove() is replaced with mgmt_pending_free() in the success path. Since mgmt_pending_valid() already unlinks the command at the beginning of the function, calling mgmt_pending_remove() leads to a double list_del() and subsequent list corruption/kernel panic. 2. In set_mesh_complete(), the use of mgmt_pending_foreach() in the error path is removed. Since the current command is already unlinked by mgmt_pending_valid(), this foreach loop would incorrectly target other pending mesh commands, potentially freeing them while they are still being processed concurrently (leading to UAFs). The redundant mgmt_cmd_status() is also simplified to use cmd->opcode directly.

Affected products

Linux kernel: from 6.6.140 before 6.7; from 6.12.59 before 6.12.78; from 6.16.10 before 6.17; from 6.17.1 before 6.18.20; from 6.19 before 6.19.10; 6.17, 7.0-rc1, 7.0-rc2, 7.0-rc3, 7.0-rc4 — fixed in 6.12.78, 6.17, 6.18.20, 6.19.10, 6.7

How to fix

Upgrade to a fixed version: Linux kernel 6.12.78, 6.17, 6.18.20, 6.19.10. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-43059 or the next vulnerability affects your stack