CVE-2022-49474
published 2025-02-26CVE-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…
PriorityP338high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.28%
19.8th percentile
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
Affected
36 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 0115a66ebb44bd9127ccb58cf43ed23c795eb1f0 < 7d61dbd7311ab978d8ddac1749a758de4de00374 | 7d61dbd7311ab978d8ddac1749a758de4de00374 |
| linux | linux | >= 059c2c09f4b7f97711d0d8eaa0b9877f5e7d0a75 < 36c644c63bfcaee2d3a426f45e89a9cd09799318 | 36c644c63bfcaee2d3a426f45e89a9cd09799318 |
| linux | linux | >= 22c66af08230a7030bdb88accffaec3424695631 < 9de3dc09e56f8deacd2bdbf4cecb71e11a312405 | 9de3dc09e56f8deacd2bdbf4cecb71e11a312405 |
| linux | linux | >= 4.14.247 < 4.14.283 | 4.14.283 |
| linux | linux | >= 4.19.207 < 4.19.247 | 4.19.247 |
| linux | linux | >= 4.4.284 < 4.5 | 4.5 |
| linux | linux | >= 4.9.283 < 4.9.318 | 4.9.318 |
| linux | linux | >= 5.10.65 < 5.10.121 | 5.10.121 |
| linux | linux | >= 5.13.17 < 5.14 | 5.14 |
| linux | linux | >= 5.14.4 < 5.15 | 5.15 |
| linux | linux | >= 5.4.146 < 5.4.198 | 5.4.198 |
| linux | linux | >= 5ccb04c6e1fb7b97fa2e1785b67c3a1cb3527ef7 < 6f55fac0af3531cf60d11369454c41f5fc81ab3f | 6f55fac0af3531cf60d11369454c41f5fc81ab3f |
| linux | linux | >= bc4b08383046f3282b6fa58cfcef05bd13e52b93 < 390d82733a953c1fabf3de9c9618091a7a9c90a6 | 390d82733a953c1fabf3de9c9618091a7a9c90a6 |
| linux | linux | >= e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 < 65d347cb39e2e6bd0c2a745ad7c928998ebb0162 | 65d347cb39e2e6bd0c2a745ad7c928998ebb0162 |
| linux | linux | >= e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 < 537f619dea4e3fa8ed1f8f938abffe3615794bcc | 537f619dea4e3fa8ed1f8f938abffe3615794bcc |
| linux | linux | >= e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 < 99df16007f4bbf9abfc3478cb17d10f0d7f8906e | 99df16007f4bbf9abfc3478cb17d10f0d7f8906e |
| linux | linux | >= e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 < 7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 | 7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-gfvc-29p2-2qqj: In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
Connecti
ghsa_unreviewed·2025-02-27
CVE-2022-49474 [HIGH] CWE-416 GHSA-gfvc-29p2-2qqj: In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
Connecti
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
OSV
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
osv·2025-02-26·CVSS 7.8
CVE-2022-49474 [HIGH] 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
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 che
Red Hat
kernel: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
vendor_redhat·2025-02-26·CVSS 7.8
CVE-2022-49474 [HIGH] kernel: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
kernel: Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout
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/0x4
Debian
CVE-2022-49474: linux - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ...
vendor_debian·2022·CVSS 7.8
CVE-2022-49474 [HIGH] CVE-2022-49474: linux - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ...
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 che
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/36c644c63bfcaee2d3a426f45e89a9cd09799318https://git.kernel.org/stable/c/390d82733a953c1fabf3de9c9618091a7a9c90a6https://git.kernel.org/stable/c/537f619dea4e3fa8ed1f8f938abffe3615794bcchttps://git.kernel.org/stable/c/65d347cb39e2e6bd0c2a745ad7c928998ebb0162https://git.kernel.org/stable/c/6f55fac0af3531cf60d11369454c41f5fc81ab3fhttps://git.kernel.org/stable/c/7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2https://git.kernel.org/stable/c/7d61dbd7311ab978d8ddac1749a758de4de00374https://git.kernel.org/stable/c/99df16007f4bbf9abfc3478cb17d10f0d7f8906ehttps://git.kernel.org/stable/c/9de3dc09e56f8deacd2bdbf4cecb71e11a312405
2025-02-26
Published