| 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: <2025122416-CVE-2023-54120-d966@gregkh> Date: Wed, 24 Dec 2025 14:07:17 +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-54120: Bluetooth: Fix race condition in hidp_session_thread From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix race condition in hidp_session_thread There is a potential race condition in hidp_session_thread that may lead to use-after-free. For instance, the timer is active while hidp_del_timer is called in hidp_session_thread(). After hidp_session_put, then 'session' will be freed, causing kernel panic when hidp_idle_timeout is running. The solution is to use del_timer_sync instead of del_timer. Here is the call trace: ? hidp_session_probe+0x780/0x780 call_timer_fn+0x2d/0x1e0 __run_timers.part.0+0x569/0x940 hidp_session_probe+0x780/0x780 call_timer_fn+0x1e0/0x1e0 ktime_get+0x5c/0xf0 lapic_next_deadline+0x2c/0x40 clockevents_program_event+0x205/0x320 run_timer_softirq+0xa9/0x1b0 __do_softirq+0x1b9/0x641 __irq_exit_rcu+0xdc/0x190 irq_exit_rcu+0xe/0x20 sysvec_apic_timer_interrupt+0xa1/0xc0 The Linux kernel CVE team has assigned CVE-2023-54120 to this issue. Affected and fixed versions =========================== Fixed in 4.14.313 with commit 152f47bd6b995e0e98c85672f6d19894bc287ef2 Fixed in 4.19.281 with commit 5f3d214d19899183d4e0cce7552998262112e4ab Fixed in 5.4.241 with commit 8a99e6200c38b78a45dcd12a6bdc43fdf4dc36be Fixed in 5.10.178 with commit f7ec5ca433ceead8d9d78fd2febff094f289441d Fixed in 5.15.108 with commit 0efb276d5848a3accc37c6f41b85e442c4768169 Fixed in 6.1.25 with commit f6719fd8f409fa1da8dc956e93822d25e1e8b360 Fixed in 6.2.12 with commit 248af9feca062a4ca9c3f2ccf67056c8a5eb817f Fixed in 6.3 with commit c95930abd687fcd1aa040dc4fe90dff947916460 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-54120 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/hidp/core.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/152f47bd6b995e0e98c85672f6d19894bc287ef2 https://git.kernel.org/stable/c/5f3d214d19899183d4e0cce7552998262112e4ab https://git.kernel.org/stable/c/8a99e6200c38b78a45dcd12a6bdc43fdf4dc36be https://git.kernel.org/stable/c/f7ec5ca433ceead8d9d78fd2febff094f289441d https://git.kernel.org/stable/c/0efb276d5848a3accc37c6f41b85e442c4768169 https://git.kernel.org/stable/c/f6719fd8f409fa1da8dc956e93822d25e1e8b360 https://git.kernel.org/stable/c/248af9feca062a4ca9c3f2ccf67056c8a5eb817f https://git.kernel.org/stable/c/c95930abd687fcd1aa040dc4fe90dff947916460
Powered by blists - more mailing lists