CVE-2022-50386: Bluetooth: L2CAP: Fix user-after-free
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: Fix user-after-free
This uses l2capchanholdunlesszero() after calling l2capgetchanblah() to prevent the following trace:
Bluetooth: l2capcore.c:static void l2capchandestroy(struct kref kref) Bluetooth: chan 0000000023c4974d Bluetooth: parent 00000000ae861c08 ================================================================== BUG: KASAN: use-after-free in mutexwaiterisfirst kernel/locking/mutex.c:191 [inline] BUG: KASAN: use-after-free in mutexlockcommon kernel/locking/mutex.c:671 [inline] BUG: KASAN: use-after-free in mutexlock+0x278/0x400 kernel/locking/mutex.c:729 Read of size 8 at addr ffff888006a49b08 by task kworker/u3:2/389
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2022-50386?
CVE-2022-50386 has been classified as a medium severity vulnerability in the Linux kernel.
What impact does CVE-2022-50386 have on affected systems?
CVE-2022-50386 can lead to user-after-free issues in Bluetooth L2CAP, potentially allowing an attacker to execute arbitrary code.
How do I fix CVE-2022-50386?
To fix CVE-2022-50386, users should update to the latest patched version of the Linux kernel provided by their distribution.
Which versions of the Linux kernel are affected by CVE-2022-50386?
CVE-2022-50386 impacts specific versions of the Linux kernel where Bluetooth L2CAP is utilized.
Is there a known exploit for CVE-2022-50386?
As of now, there are no publicly known exploits specifically targeting CVE-2022-50386.