| 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: <2025050210-CVE-2023-53063-a2c2@gregkh> Date: Fri, 2 May 2025 17:55:28 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2023-53063: Bluetooth: btsdio: fix use after free bug in btsdio_remove due to unfinished work From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btsdio: fix use after free bug in btsdio_remove due to unfinished work In btsdio_probe, &data->work was bound with btsdio_work.In btsdio_send_frame, it was started by schedule_work. If we call btsdio_remove with an unfinished job, there may be a race condition and cause UAF bug on hdev. The Linux kernel CVE team has assigned CVE-2023-53063 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.24 with commit ddbaf13e3609442b64abb931ac21527772d87980 and fixed in 4.14.312 with commit 95eacef5692545f199fae4e52abfbfa273acb351 Issue introduced in 2.6.24 with commit ddbaf13e3609442b64abb931ac21527772d87980 and fixed in 4.19.280 with commit af4d48754d5517d33bac5e504ff1f1de0808e29e Issue introduced in 2.6.24 with commit ddbaf13e3609442b64abb931ac21527772d87980 and fixed in 5.4.240 with commit a18fb433ceb56e0787546a9d77056dd0f215e762 Issue introduced in 2.6.24 with commit ddbaf13e3609442b64abb931ac21527772d87980 and fixed in 5.10.177 with commit da3d3fdfb4d523c5da30e35a8dd90e04f0fd8962 Issue introduced in 2.6.24 with commit ddbaf13e3609442b64abb931ac21527772d87980 and fixed in 5.15.105 with commit 8efae2112d910d8e5166dd0a836791b08721eef1 Issue introduced in 2.6.24 with commit ddbaf13e3609442b64abb931ac21527772d87980 and fixed in 6.1.22 with commit cbf8deacb7053ce3e3fed64b277c6c6989e65bba Issue introduced in 2.6.24 with commit ddbaf13e3609442b64abb931ac21527772d87980 and fixed in 6.2.9 with commit c59c65a14e8f7d738429648833f3bb3f9df0513f Issue introduced in 2.6.24 with commit ddbaf13e3609442b64abb931ac21527772d87980 and fixed in 6.3 with commit 1e9ac114c4428fdb7ff4635b45d4f46017e8916f 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-53063 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: drivers/bluetooth/btsdio.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/95eacef5692545f199fae4e52abfbfa273acb351 https://git.kernel.org/stable/c/af4d48754d5517d33bac5e504ff1f1de0808e29e https://git.kernel.org/stable/c/a18fb433ceb56e0787546a9d77056dd0f215e762 https://git.kernel.org/stable/c/da3d3fdfb4d523c5da30e35a8dd90e04f0fd8962 https://git.kernel.org/stable/c/8efae2112d910d8e5166dd0a836791b08721eef1 https://git.kernel.org/stable/c/cbf8deacb7053ce3e3fed64b277c6c6989e65bba https://git.kernel.org/stable/c/c59c65a14e8f7d738429648833f3bb3f9df0513f https://git.kernel.org/stable/c/1e9ac114c4428fdb7ff4635b45d4f46017e8916f
Powered by blists - more mailing lists