Bluetooth: L2CAP: Fix user-after-free
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3df91ea20e744344100b10ae69a17211fcf5b207 · < d1e894f950ad48897d1a7cb05909ea29d8c3810e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: Fix user-after-free
This uses l2cap_chan_hold_unless_zero() after calling __l2cap_get_chan_blah() to prevent the following trace:
Bluetooth: l2cap_core.c:static void l2cap_chan_destroy(struct kref *kref) Bluetooth: chan 0000000023c4974d Bluetooth: parent 00000000ae861c08 ================================================================== BUG: KASAN: use-after-free in __mutex_waiter_is_first kernel/locking/mutex.c:191 [inline] BUG: KASAN: use-after-free in __mutex_lock_common kernel/locking/mutex.c:671 [inline] BUG: KASAN: use-after-free in __mutex_lock+0x278/0x400 kernel/locking/mutex.c:729 Read of size 8 at addr ffff888006a49b08 by task kworker/u3:2/389
From the CVE record · Linux
The Linux kernel’s Bluetooth L2CAP code has a use-after-free vulnerability that can trigger an invalid memory access. The input does not specify what an attacker can do, whether authentication or user interaction is required, or whether exploitation is local or remote.
Engineers running Linux kernels with Bluetooth L2CAP should check their versions; affected versions are not specified.