CVE-2026-43059 Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers
A use-after-free and list corruption vulnerability in the Linux kernel Bluetooth MGMT subsystem allows attackers to cause denial of service or execute arbitrary code.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-43059?
CVE-2026-43059 is a high-severity use after free vulnerability in Linux kernel, published on 5 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Weakness: CWE-416
Which versions are affected by CVE-2026-43059?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2026-43059?
Apply the vendor's patch.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2026-43059 being exploited?
There is no known exploitation of CVE-2026-43059 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as AZL-89670, BELL-CVE-2026-43059, DEBIAN-CVE-2026-43059, GHSA-9xxq-2x8g-75gf, ROOT-OS-UBUNTU-2404-CVE-2026-43059, UBUNTU-CVE-2026-43059.