Answer in brief
CVE-2022-49474 records a Unknown severity vulnerability in Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2022-49474 records a Unknown severity vulnerability in Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=22c66af08230a7030bdb88accffaec3424695631 <9de3dc09e56f8deacd2bdbf4cecb71e11a312405 || >=0115a66ebb44bd9127ccb58cf43ed23c795eb1f0 <7d61dbd7311ab978d8ddac1749a758de4de00374 || >=bc4b08383046f3282b6fa58cfcef05bd13e52b93 <390d82733a953c1fabf3de9c9618091a7a9c90a6 || >=5ccb04c6e1fb7b97fa2e1785b67c3a1cb3527ef7 <6f55fac0af3531cf60d11369454c41f5fc81ab3f || >=059c2c09f4b7f97711d0d8eaa0b9877f5e7d0a75 <36c644c63bfcaee2d3a426f45e89a9cd09799318 || >=e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 <65d347cb39e2e6bd0c2a745ad7c928998ebb0162 || >=e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 <537f619dea4e3fa8ed1f8f938abffe3615794bcc || >=e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 <99df16007f4bbf9abfc3478cb17d10f0d7f8906e || >=e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 <7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 || 98ae477ed1540d3acbbf44d88ee237ad64275158 || f0c389e23e2475e5837716a629c81b7a9d90cc94 || 0b9da4bde0d59c61b3675bdd80a05a726beb875a || >=4.9.283 <4.9.318 || >=4.14.247 <4.14.283 || >=4.19.207 <4.19.247 || >=5.4.146 <5.4.198 || >=5.10.65 <5.10.121 || >=4.4.284 <4.5 || >=5.13.17 <5.14 || >=5.14.4 <5.15 | 9de3dc09e56f8deacd2bdbf4cecb71e11a312405, 7d61dbd7311ab978d8ddac1749a758de4de00374, 390d82733a953c1fabf3de9c9618091a7a9c90a6, 6f55fac0af3531cf60d11369454c41f5fc81ab3f, 36c644c63bfcaee2d3a426f45e89a9cd09799318, 65d347cb39e2e6bd0c2a745ad7c928998ebb0162, 537f619dea4e3fa8ed1f8f938abffe3615794bcc, 99df16007f4bbf9abfc3478cb17d10f0d7f8906e, 7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2, 4.9.318, 4.14.283, 4.19.247, 5.4.198, 5.10.121, 4.5, 5.14, 5.15 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=22c66af08230a7030bdb88accffaec3424695631 <9de3dc09e56f8deacd2bdbf4cecb71e11a312405 || >=0115a66ebb44bd9127ccb58cf43ed23c795eb1f0 <7d61dbd7311ab978d8ddac1749a758de4de00374 || >=bc4b08383046f3282b6fa58cfcef05bd13e52b93 <390d82733a953c1fabf3de9c9618091a7a9c90a6 || >=5ccb04c6e1fb7b97fa2e1785b67c3a1cb3527ef7 <6f55fac0af3531cf60d11369454c41f5fc81ab3f || >=059c2c09f4b7f97711d0d8eaa0b9877f5e7d0a75 <36c644c63bfcaee2d3a426f45e89a9cd09799318 || >=e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 <65d347cb39e2e6bd0c2a745ad7c928998ebb0162 || >=e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 <537f619dea4e3fa8ed1f8f938abffe3615794bcc || >=e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 <99df16007f4bbf9abfc3478cb17d10f0d7f8906e || >=e1dee2c1de2b4dd00eb44004a4bda6326ed07b59 <7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 || 98ae477ed1540d3acbbf44d88ee237ad64275158 || f0c389e23e2475e5837716a629c81b7a9d90cc94 || 0b9da4bde0d59c61b3675bdd80a05a726beb875a || >=4.9.283 <4.9.318 || >=4.14.247 <4.14.283 || >=4.19.207 <4.19.247 || >=5.4.146 <5.4.198 || >=5.10.65 <5.10.121 || >=4.4.284 <4.5 || >=5.13.17 <5.14 || >=5.14.4 <5.15 | 9de3dc09e56f8deacd2bdbf4cecb71e11a312405, 7d61dbd7311ab978d8ddac1749a758de4de00374, 390d82733a953c1fabf3de9c9618091a7a9c90a6, 6f55fac0af3531cf60d11369454c41f5fc81ab3f, 36c644c63bfcaee2d3a426f45e89a9cd09799318, 65d347cb39e2e6bd0c2a745ad7c928998ebb0162, 537f619dea4e3fa8ed1f8f938abffe3615794bcc, 99df16007f4bbf9abfc3478cb17d10f0d7f8906e, 7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2, 4.9.318, 4.14.283, 4.19.247, 5.4.198, 5.10.121, 4.5, 5.14, 5.15 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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
Quoted source text, attributed separately from HOL analysis.