Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.78, 6.17, 6.18.20, 6.19.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a · fixed in 3d6de8467236cd763ddc7d06127689bdfbfbd8ff; From d71b98f253b079cbadc83266383f26fe7e9e103b · fixed in 695b45b2262fcb5e71bed1175aad59c72f92aa78; From 302a1f674c00dd5581ab8e493ef44767c5101aab · fixed in b5c5e96f3b0a5003c3ff98ebb33e59afec51dd77; From 302a1f674c00dd5581ab8e493ef44767c5101aab · fixed in 02023ff760cc104a5d86a82ef5b8dd89098ad78d; From 302a1f674c00dd5581ab8e493ef44767c5101aab · fixed in 17f89341cb4281d1da0e2fb0de5406ab7c4e25ef; From 6.6.140 · fixed in 6.6.160; From 6.12.59 · fixed in 6.12.78; From 6.16.10 · fixed in 6.17
- Linux Linux
6.17
- KernelLinux
fixed in 6.6.160; From 6.7.0 · fixed in 6.12.78; From 6.13.0 · fixed in 6.18.20; From 6.17.0 · fixed in 6.19.10