CVE-2022-49474

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/99df16007f4bbf9abfc3478cb17d10f0d7f8906e
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/537f619dea4e3fa8ed1f8f938abffe3615794bcc
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65d347cb39e2e6bd0c2a745ad7c928998ebb0162
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/36c644c63bfcaee2d3a426f45e89a9cd09799318
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f55fac0af3531cf60d11369454c41f5fc81ab3f
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/390d82733a953c1fabf3de9c9618091a7a9c90a6
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d61dbd7311ab978d8ddac1749a758de4de00374
generic

Bluetooth: fix dangling sco_conn and use-after-free in sco_sock_timeout - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9de3dc09e56f8deacd2bdbf4cecb71e11a312405

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.9.318—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 116 total refreshes for this CVE.

  1. 2026-08-07 16:24 UTCEPSS rescore
  2. 2026-08-06 13:44 UTCEPSS rescore
  3. 2026-08-05 19:15 UTCEPSS rescore
  4. 2026-08-05 09:31 UTCEG score recompute
  5. 2026-08-05 09:31 UTCGHSA enrichment
  6. 2026-08-04 15:07 UTCEPSS rescore
  7. 2026-08-04 10:35 UTCEPSS rescore
  8. 2026-08-04 09:46 UTCEG score recompute
  9. 2026-08-04 09:46 UTCGHSA enrichment
  10. 2026-08-03 10:33 UTCEPSS rescore
  11. 2026-08-01 04:13 UTCEPSS rescore
  12. 2026-08-01 04:13 UTCEPSS rescore
  13. 2026-07-30 16:25 UTCEPSS rescore
  14. 2026-07-30 01:28 UTCEPSS rescore
  15. 2026-07-28 15:34 UTCEPSS rescore
  16. 2026-07-26 14:52 UTCEPSS rescore
  17. 2026-07-26 14:52 UTCEPSS rescore
  18. 2026-07-25 14:16 UTCEPSS rescore
  19. 2026-07-24 14:15 UTCEPSS rescore
  20. 2026-07-24 14:11 UTCOSV refresh
  21. 2026-07-23 14:16 UTCEPSS rescore
  22. 2026-07-23 14:16 UTCEPSS rescore
  23. 2026-07-23 02:16 UTCEG score recompute
  24. 2026-07-22 23:04 UTCEG score recompute
  25. 2026-07-22 14:06 UTCEPSS rescore
Show 75 more
  1. 2026-07-22 14:06 UTCEPSS rescore
  2. 2026-07-21 15:23 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-20 17:05 UTCEPSS rescore
  5. 2026-07-19 14:29 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-19 02:27 UTCEPSS rescore
  8. 2026-07-19 02:27 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-16 17:00 UTCEPSS rescore
  12. 2026-07-15 16:56 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 01:58 UTCEPSS rescore
  15. 2026-07-15 01:58 UTCEPSS rescore
  16. 2026-07-13 22:28 UTCEPSS rescore
  17. 2026-07-13 22:28 UTCEPSS rescore
  18. 2026-07-13 06:11 UTCEPSS rescore
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-12 05:44 UTCEPSS rescore
  21. 2026-07-11 08:25 UTCEPSS rescore
  22. 2026-07-11 08:25 UTCEPSS rescore
  23. 2026-07-09 19:08 UTCEPSS rescore
  24. 2026-07-08 15:13 UTCEPSS rescore
  25. 2026-07-07 13:44 UTCEPSS rescore
  26. 2026-07-07 09:51 UTCOSV refresh
  27. 2026-07-06 16:25 UTCEPSS rescore
  28. 2026-07-06 02:21 UTCEPSS rescore
  29. 2026-07-05 02:28 UTCEPSS rescore
  30. 2026-07-04 06:29 UTCEPSS rescore
  31. 2026-07-01 15:04 UTCEPSS rescore
  32. 2026-06-30 23:21 UTCEPSS rescore
  33. 2026-06-30 23:20 UTCEPSS rescore
  34. 2026-06-29 14:04 UTCEPSS rescore
  35. 2026-06-28 14:06 UTCEPSS rescore
  36. 2026-06-28 04:54 UTCEPSS rescore
  37. 2026-06-28 04:54 UTCEPSS rescore
  38. 2026-06-27 03:07 UTCEPSS rescore
  39. 2026-06-27 03:07 UTCEPSS rescore
  40. 2026-06-25 13:48 UTCEPSS rescore
  41. 2026-06-25 13:48 UTCEPSS rescore
  42. 2026-06-24 14:03 UTCEPSS rescore
  43. 2026-06-24 14:03 UTCEPSS rescore
  44. 2026-06-23 21:31 UTCEPSS rescore
  45. 2026-06-23 21:31 UTCEPSS rescore
  46. 2026-06-22 14:24 UTCEPSS rescore
  47. 2026-06-21 14:55 UTCEPSS rescore
  48. 2026-06-21 14:55 UTCEPSS rescore
  49. 2026-06-21 01:58 UTCEPSS rescore
  50. 2026-06-21 01:58 UTCEPSS rescore
  51. 2026-06-19 19:24 UTCEPSS rescore
  52. 2026-06-19 19:24 UTCEPSS rescore
  53. 2026-06-18 20:43 UTCOSV refresh
  54. 2026-06-18 17:51 UTCEPSS rescore
  55. 2026-06-18 17:51 UTCEPSS rescore
  56. 2026-06-17 17:51 UTCEPSS rescore
  57. 2026-06-17 17:51 UTCEPSS rescore
  58. 2026-06-16 17:51 UTCEPSS rescore
  59. 2026-06-16 17:51 UTCEPSS rescore
  60. 2026-06-15 17:47 UTCEPSS rescore
  61. 2026-06-14 23:16 UTCEPSS rescore
  62. 2026-06-13 22:59 UTCEPSS rescore
  63. 2026-06-12 23:10 UTCEPSS rescore
  64. 2026-06-12 23:10 UTCEPSS rescore
  65. 2026-06-11 13:58 UTCEPSS rescore
  66. 2026-06-11 13:58 UTCEPSS rescore
  67. 2026-06-10 13:21 UTCEPSS rescore
  68. 2026-06-10 13:21 UTCEPSS rescore
  69. 2026-06-08 14:15 UTCEPSS rescore
  70. 2026-06-08 14:15 UTCEPSS rescore
  71. 2026-06-07 15:23 UTCEPSS rescore
  72. 2026-06-07 15:23 UTCEPSS rescore
  73. 2026-06-06 13:46 UTCEPSS rescore
  74. 2026-06-06 13:46 UTCEPSS rescore
  75. 2026-06-05 22:46 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-49474?
CVE-2022-49474 is a high vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix dangling scoconn and use-after-free in scosock_timeout Connecting the same socket twice consecutively in scosockconnect() could lead to a race condition where two sco_conn objects are created but only one is…
When was CVE-2022-49474 disclosed?
CVE-2022-49474 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49474 actively exploited?
CVE-2022-49474 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.3% of all scored CVEs.
What is the CVSS score of CVE-2022-49474?
CVE-2022-49474 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49474?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49474, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-49474

Explore →

Is Your Infrastructure Affected by CVE-2022-49474?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs