CVE-2022-48790

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2024-07-16. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.0Exploit: 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:

nvme: fix a possible use-after-free in controller reset during load

Unlike .queue_rq, in .submit_async_event drivers may not check the ctrl readiness for AER submission. This may lead to a use-after-free condition that was observed with nvme-tcp.

The race condition may happen in the following scenario:

  • driver executes its reset_ctrl_work
  • -> nvme_stop_ctrl - flushes ctrl async_event_work
  • ctrl sends AEN which is received by the host, which in turn
schedules AEN handling
  • teardown admin queue (which releases the queue socket)
  • AEN processed, submits another AER, calling the driver to submit
  • driver attempts to send the cmd
==> use-after-free

In order to fix that, add ctrl state check to validate the ctrl is actually able to accept the AER submission.

This addresses the above race in controller resets because the driver during teardown should:

  • change ctrl state to RESETTING
  • flush async_event_work (as well as other async work elements)

So after 1,2, any other AER command will find the ctrl state to be RESETTING and bail out without submitting the AER.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity70% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

July 16, 2024

Last Modified

August 5, 2026

Advisory Details (6)

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

nvme: fix a possible use-after-free in controller reset during load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d
generic

nvme: fix a possible use-after-free in controller reset during load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861
generic

nvme: fix a possible use-after-free in controller reset during load - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: fix a possible use-after-free in controller reset during load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f
generic

nvme: fix a possible use-after-free in controller reset during load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765
generic

nvme: fix a possible use-after-free in controller reset during load - kernel/git/stable/linux.git - Linux kernel stable tree

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

Patch Availability(1)

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

Frequently asked(5)

What is CVE-2022-48790?
CVE-2022-48790 is a high vulnerability published on July 16, 2024. In the Linux kernel, the following vulnerability has been resolved: nvme: fix a possible use-after-free in controller reset during load Unlike .queuerq, in .submitasync_event drivers may not check the ctrl readiness for AER submission. This may lead to a use-after-free condition that was observed…
When was CVE-2022-48790 disclosed?
CVE-2022-48790 was first published in the National Vulnerability Database on July 16, 2024, 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-48790 actively exploited?
CVE-2022-48790 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.3% of all scored CVEs.
What is the CVSS score of CVE-2022-48790?
CVE-2022-48790 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2022-48790?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-48790, 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-48790

Explore →

Is Your Infrastructure Affected by CVE-2022-48790?

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

Start Free Scan →Browse All CVEs