| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025123025-CVE-2023-54214-c4a6@gregkh> Date: Tue, 30 Dec 2025 13:13:44 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-54214: Bluetooth: L2CAP: Fix potential user-after-free From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix potential user-after-free This fixes all instances of which requires to allocate a buffer calling alloc_skb which may release the chan lock and reacquire later which makes it possible that the chan is disconnected in the meantime. The Linux kernel CVE team has assigned CVE-2023-54214 to this issue. Affected and fixed versions =========================== Issue introduced in 3.5 with commit a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 and fixed in 4.14.308 with commit b2fde8cb2a25125111f2144604e0e7c0ebcc4bba Issue introduced in 3.5 with commit a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 and fixed in 4.19.276 with commit a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49 Issue introduced in 3.5 with commit a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 and fixed in 5.4.235 with commit 60aaccf16d1e099c16bebfb96428ae762cb528f7 Issue introduced in 3.5 with commit a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 and fixed in 5.10.173 with commit b8ed41cc04fb74005aa51d17865ca3d022760335 Issue introduced in 3.5 with commit a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 and fixed in 5.15.99 with commit 31a288a4df7f6a28e65da22a4ab2add4a963738e Issue introduced in 3.5 with commit a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 and fixed in 6.1.16 with commit 64e28ecf44e46de9f01915a4146706a21c3469d2 Issue introduced in 3.5 with commit a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 and fixed in 6.2.3 with commit 994e3e18908f5c4a12d07b44018e6aa85f071048 Issue introduced in 3.5 with commit a6a5568c03c4805d4d250f6bd9d468eeeb4ea059 and fixed in 6.3 with commit df5703348813235874d851934e957c3723d71644 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2023-54214 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: net/bluetooth/l2cap_core.c net/bluetooth/l2cap_sock.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/b2fde8cb2a25125111f2144604e0e7c0ebcc4bba https://git.kernel.org/stable/c/a6a7d1541fefddf7ca0cfb34c1bff63ff809cc49 https://git.kernel.org/stable/c/60aaccf16d1e099c16bebfb96428ae762cb528f7 https://git.kernel.org/stable/c/b8ed41cc04fb74005aa51d17865ca3d022760335 https://git.kernel.org/stable/c/31a288a4df7f6a28e65da22a4ab2add4a963738e https://git.kernel.org/stable/c/64e28ecf44e46de9f01915a4146706a21c3469d2 https://git.kernel.org/stable/c/994e3e18908f5c4a12d07b44018e6aa85f071048 https://git.kernel.org/stable/c/df5703348813235874d851934e957c3723d71644
Powered by blists - more mailing lists