CVE-2022-49474
"Linux Bluetooth SCO Socket Use-After-Free Vulnerability"
Description
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
INFO
Published Date :
Feb. 26, 2025, 7:01 a.m.
Last Modified :
March 24, 2025, 7:59 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
5.9
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-49474.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-49474 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-49474 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 24, 2025
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 5.17.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.18 up to (excluding) 5.18.3 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.14.247 up to (excluding) 4.14.283 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.19.207 up to (excluding) 4.19.247 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.4.284 up to (excluding) 4.5 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.9.238 up to (excluding) 4.9.318 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.4.146 up to (excluding) 5.4.198 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.65 up to (excluding) 5.10.121 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.13.17 up to (excluding) 5.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.14.4 up to (excluding) 5.15.46 Added Reference Type kernel.org: https://git.kernel.org/stable/c/36c644c63bfcaee2d3a426f45e89a9cd09799318 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/390d82733a953c1fabf3de9c9618091a7a9c90a6 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/537f619dea4e3fa8ed1f8f938abffe3615794bcc Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/65d347cb39e2e6bd0c2a745ad7c928998ebb0162 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/6f55fac0af3531cf60d11369454c41f5fc81ab3f Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/7d61dbd7311ab978d8ddac1749a758de4de00374 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/99df16007f4bbf9abfc3478cb17d10f0d7f8906e Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/9de3dc09e56f8deacd2bdbf4cecb71e11a312405 Types: Patch -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Feb. 27, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Added CWE CWE-416 -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Feb. 26, 2025
Action Type Old Value New Value Added Description 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 Added Reference https://git.kernel.org/stable/c/36c644c63bfcaee2d3a426f45e89a9cd09799318 Added Reference https://git.kernel.org/stable/c/390d82733a953c1fabf3de9c9618091a7a9c90a6 Added Reference https://git.kernel.org/stable/c/537f619dea4e3fa8ed1f8f938abffe3615794bcc Added Reference https://git.kernel.org/stable/c/65d347cb39e2e6bd0c2a745ad7c928998ebb0162 Added Reference https://git.kernel.org/stable/c/6f55fac0af3531cf60d11369454c41f5fc81ab3f Added Reference https://git.kernel.org/stable/c/7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 Added Reference https://git.kernel.org/stable/c/7d61dbd7311ab978d8ddac1749a758de4de00374 Added Reference https://git.kernel.org/stable/c/99df16007f4bbf9abfc3478cb17d10f0d7f8906e Added Reference https://git.kernel.org/stable/c/9de3dc09e56f8deacd2bdbf4cecb71e11a312405
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-49474 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-49474
weaknesses.