CVE-2022-49474

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout<br /> <br /> Connecting the same socket twice consecutively in sco_sock_connect()<br /> could lead to a race condition where two sco_conn objects are created<br /> but only one is associated with the socket. If the socket is closed<br /> before the SCO connection is established, the timer associated with the<br /> dangling sco_conn object won&amp;#39;t be canceled. As the sock object is being<br /> freed, the use-after-free problem happens when the timer callback<br /> function sco_sock_timeout() accesses the socket. Here&amp;#39;s the call trace:<br /> <br /> dump_stack+0x107/0x163<br /> ? refcount_inc+0x1c/<br /> print_address_description.constprop.0+0x1c/0x47e<br /> ? refcount_inc+0x1c/0x7b<br /> kasan_report+0x13a/0x173<br /> ? refcount_inc+0x1c/0x7b<br /> check_memory_region+0x132/0x139<br /> refcount_inc+0x1c/0x7b<br /> sco_sock_timeout+0xb2/0x1ba<br /> process_one_work+0x739/0xbd1<br /> ? cancel_delayed_work+0x13f/0x13f<br /> ? __raw_spin_lock_init+0xf0/0xf0<br /> ? to_kthread+0x59/0x85<br /> worker_thread+0x593/0x70e<br /> kthread+0x346/0x35a<br /> ? drain_workqueue+0x31a/0x31a<br /> ? kthread_bind+0x4b/0x4b<br /> ret_from_fork+0x1f/0x30