CVE-2026-43059Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 4 days later
· 4 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a – < 3d6de8467236cd763ddc7d06127689bdfbfbd8ff
- affected d71b98f253b079cbadc83266383f26fe7e9e103b – < 695b45b2262fcb5e71bed1175aad59c72f92aa78
- affected 302a1f674c00dd5581ab8e493ef44767c5101aab – < b5c5e96f3b0a5003c3ff98ebb33e59afec51dd77
- affected 302a1f674c00dd5581ab8e493ef44767c5101aab – < 02023ff760cc104a5d86a82ef5b8dd89098ad78d
- affected 302a1f674c00dd5581ab8e493ef44767c5101aab – < 17f89341cb4281d1da0e2fb0de5406ab7c4e25ef
- affected 87a1f16f07c6c43771754075e08f45b41d237421
- affected 6.6.140 – < 6.6.160
- affected 6.12.59 – < 6.12.78
- affected 6.16.10 – < 6.17
- affected 6.17
- unaffected < 6.17
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.18.20 – ≤ 6.18.*
- unaffected 6.19.10 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References5
- https://git.kernel.org/stable/c/3d6de8467236cd763ddc7d06127689bdfbfbd8ff (opens in a new tab)
- https://git.kernel.org/stable/c/695b45b2262fcb5e71bed1175aad59c72f92aa78 (opens in a new tab)
- https://git.kernel.org/stable/c/b5c5e96f3b0a5003c3ff98ebb33e59afec51dd77 (opens in a new tab)
- https://git.kernel.org/stable/c/02023ff760cc104a5d86a82ef5b8dd89098ad78d (opens in a new tab)
- https://git.kernel.org/stable/c/17f89341cb4281d1da0e2fb0de5406ab7c4e25ef (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-27351 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43059)Record last updated .