Tracker / CVE-2022-49474
CVE-2022-49474
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout Connecting the same socket twice consecutively in sco_sock_connect() could lead to a race condition where two sco_conn objects are created but only one is associated with the socket. If the socket is closed before the SCO connection is established, the timer associated with the dangling sco_conn object won't be canceled. As the sock object is being freed, the use-after-free problem happens when the timer callback function sco_sock_timeout() accesses the socket. Here's the call trace: dump_stack+0x107/0x163 ? refcount_inc+0x1c/ print_address_description.constprop.0+0x1c/0x47e ? refcount_inc+0x1c/0x7b kasan_report+0x13a/0x173 ? refcount_inc+0x1c/0x7b check_memory_region+0x132/0x139 refcount_inc+0x1c/0x7b sco_sock_timeout+0xb2/0x1ba process_one_work+0x739/0xbd1 ? cancel_delayed_work+0x13f/0x13f ? __raw_spin_lock_init+0xf0/0xf0 ? to_kthread+0x59/0x85 worker_thread+0x593/0x70e kthread+0x346/0x35a ? drain_workqueue+0x31a/0x31a ? kthread_bind+0x4b/0x4b ret_from_fork+0x1f/0x30
Prodotti e versioni affette
| linux | linux_kernel · 4.14.247 → 4.14.283 |
|---|---|
| linux | linux_kernel · 4.19.207 → 4.19.247 |
| linux | linux_kernel · 4.4.284 → 4.5 |
| linux | linux_kernel · 4.9.238 → 4.9.318 |
| linux | linux_kernel · 5.10.65 → 5.10.121 |
| linux | linux_kernel · 5.13.17 → 5.14 |
| linux | linux_kernel · 5.14.4 → 5.15.46 |
| linux | linux_kernel · 5.16 → 5.17.14 |
| linux | linux_kernel · 5.18 → 5.18.3 |
| linux | linux_kernel · 5.4.146 → 5.4.198 |