Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2022-49474

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.9.318, 4.14.283, 4.19.247, 5.4.198, 5.10.121, and 3 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

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

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From 4.9.283 · fixed in 4.9.318; From 4.14.247 · fixed in 4.14.283; From 4.19.207 · fixed in 4.19.247; From 5.4.146 · fixed in 5.4.198; From 5.10.65 · fixed in 5.10.121; From 4.4.284 · fixed in 4.5; From 5.13.17 · fixed in 5.14; From 5.14.4 · fixed in 5.15

  • Linux Linux

    5.15

References 9

git.kernel.org