CVE-2022-50552

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

blk-mq: use quiesced elevator switch when reinitializing queues

The hctx's run_work may be racing with the elevator switch when reinitializing hardware queues. The queue is merely frozen in this context, but that only prevents requests from allocating and doesn't stop the hctx work from running. The work may get an elevator pointer that's being torn down, and can result in use-after-free errors and kernel panics (example below). Use the quiesced elevator switch instead, and make the previous one static since it is now only used locally.

nvme nvme0: resetting controller nvme nvme0: 32/0/0 default/read/poll queues BUG: kernel NULL pointer dereference, address: 0000000000000008 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 80000020c8861067 P4D 80000020c8861067 PUD 250f8c8067 PMD 0 Oops: 0000 [#1] SMP PTI Workqueue: kblockd blk_mq_run_work_fn RIP: 0010:kyber_has_work+0x29/0x70

...

Call Trace: __blk_mq_do_dispatch_sched+0x83/0x2b0 __blk_mq_sched_dispatch_requests+0x12e/0x170 blk_mq_sched_dispatch_requests+0x30/0x60 __blk_mq_run_hw_queue+0x2b/0x50 process_one_work+0x1ef/0x380 worker_thread+0x2d/0x3e0

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

Published

October 7, 2025

Last Modified

June 1, 2026

Advisory Details (5)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

blk-mq: use quiesced elevator switch when reinitializing queues - kernel/git/stable/linux.git - Linux kernel stable tree

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

blk-mq: use quiesced elevator switch when reinitializing queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9646443f28f33ec545ae303e613c3f476fad4dc1
generic

blk-mq: use quiesced elevator switch when reinitializing queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8237c01f1696bc53c470493bf1fe092a107648a6
generic

blk-mq: use quiesced elevator switch when reinitializing queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63a681bcc32a43528ce0f690569f7f48e59c3963
generic

blk-mq: use quiesced elevator switch when reinitializing queues - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f90015383cd3f1128bebfbe7a97122d97808046

Vendor Advisories for CVE-2022-50552(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.258—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 9× in last 7d / 45× 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 110 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-50552?
CVE-2022-50552 is a high vulnerability published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: blk-mq: use quiesced elevator switch when reinitializing queues The hctx's run_work may be racing with the elevator switch when reinitializing hardware queues. The queue is merely frozen in this context, but that only prevents…
When was CVE-2022-50552 disclosed?
CVE-2022-50552 was first published in the National Vulnerability Database on October 7, 2025, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50552 actively exploited?
CVE-2022-50552 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-50552?
CVE-2022-50552 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50552?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50552, 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-50552

Explore →

Is Your Infrastructure Affected by CVE-2022-50552?

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

Start Free Scan →Browse All CVEs