CVE-2026-43059

Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers

HIGH
7.8
CVSS Score
Published: May 5, 2026 at 03:17 PM UTC
Updated: October 21, 2026 at 01:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.12.59 ≤ v < 6.12.786.16.10 ≤ v < 6.176.17.1 ≤ v < 6.18.206.19 ≤ v < 6.19.106.6.140 ≤ v < 6.70b60eb04b8524e1b4b3f07fea0d16fda9a677d9a302a1f674c00dd5581ab8e493ef44767c5101aab6.12.596.16.106.176.6.1407.07.0 rc17.0 rc27.0 rc37.0 rc487a1f16f07c6c43771754075e08f45b41d237421d71b98f253b079cbadc83266383f26fe7e9e103b
Vendor states this is fixed in 02023ff760cc104a5d86a82ef5b8dd89098ad78d (fixed)
Vendor states this is fixed in 17f89341cb4281d1da0e2fb0de5406ab7c4e25ef (fixed)
Vendor states this is fixed in 695b45b2262fcb5e71bed1175aad59c72f92aa78 (fixed)
Vendor states this is fixed in b5c5e96f3b0a5003c3ff98ebb33e59afec51dd77 (fixed)
Vendor states this is fixed in 6.12.78 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.18.20 (unaffected)
Vendor states this is fixed in 6.19.10 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.0 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card