CVE-2022-49309

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-03-17. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: 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:

drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()

There is a deadlock in rtw_surveydone_event_callback(), which is shown below:

(Thread 1) | (Thread 2) | _set_timer() rtw_surveydone_event_callback()| mod_timer() spin_lock_bh() //(1) | (wait a time) ... | rtw_scan_timeout_handler() del_timer_sync() | spin_lock_bh() //(2) (wait timer to stop) | ...

We hold pmlmepriv->lock in position (1) of thread 1 and use del_timer_sync() to wait timer to stop, but timer handler also need pmlmepriv->lock in position (2) of thread 2. As a result, rtw_surveydone_event_callback() will block forever.

This patch extracts del_timer_sync() from the protection of spin_lock_bh(), which could let timer handler to obtain the needed lock. What`s more, we change spin_lock_bh() in rtw_scan_timeout_handler() to spin_lock_irq(). Otherwise, spin_lock_bh() will also cause deadlock() in timer handler.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

February 26, 2025

Last Modified

August 13, 2026

Advisory Details (5)

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

drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc7ad0d77b51c872d629bcd98aea463a3c4109e7
generic

drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c41f5c341853f84b7bc2f32605d4e2782e8c279
generic

drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ce129d3efd181da5fd56f4360cc8827122afa67e
generic

drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f89f6c3ebf69623b8ea48200bd690e9e210335a1
generic

drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c84e5c819600ee0628f61b33d145258ae0f3d7a7

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.237osv

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (45 versions)5.10.237-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux5.18.5-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux5.18.5-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux5.18.5-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 24× 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 150 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-49309?
CVE-2022-49309 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8723bs: Fix deadlock in rtwsurveydoneevent_callback() There is a deadlock in rtwsurveydoneevent_callback(), which is shown below: (Thread 1) | (Thread 2) | settimer() rtwsurveydoneeventcallback()| modtimer()…
When was CVE-2022-49309 disclosed?
CVE-2022-49309 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49309 actively exploited?
CVE-2022-49309 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 90.5% of all scored CVEs.
What is the CVSS score of CVE-2022-49309?
CVE-2022-49309 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49309, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49309

Explore →

Is Your Infrastructure Affected by CVE-2022-49309?

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