CVE-2022-48790
"NVMe Linux kernel Use-After-Free Vulnerability"
Description
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: 1. driver executes its reset_ctrl_work 2. -> nvme_stop_ctrl - flushes ctrl async_event_work 3. ctrl sends AEN which is received by the host, which in turn schedules AEN handling 4. teardown admin queue (which releases the queue socket) 5. AEN processed, submits another AER, calling the driver to submit 6. 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: 1. change ctrl state to RESETTING 2. 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.
INFO
Published Date :
July 16, 2024, 12:15 p.m.
Last Modified :
Nov. 21, 2024, 7:34 a.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
5.9
Exploitability Score :
1.0
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2022-48790
.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2022-48790
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2022-48790
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f Added Reference https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d Added Reference https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765 Added Reference https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861 Added Reference https://git.kernel.org/stable/c/a25e460fbb0340488d119fb2e28fe3f829b7417e Added Reference https://git.kernel.org/stable/c/e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 -
Initial Analysis by [email protected]
Aug. 07, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f No Types Assigned https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f Patch Changed Reference Type https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d No Types Assigned https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d Patch Changed Reference Type https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765 No Types Assigned https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765 Patch Changed Reference Type https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861 No Types Assigned https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861 Patch Changed Reference Type https://git.kernel.org/stable/c/a25e460fbb0340488d119fb2e28fe3f829b7417e No Types Assigned https://git.kernel.org/stable/c/a25e460fbb0340488d119fb2e28fe3f829b7417e Patch Changed Reference Type https://git.kernel.org/stable/c/e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 No Types Assigned https://git.kernel.org/stable/c/e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 Patch Added CWE NIST CWE-416 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 4.19.231 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.181 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.102 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.25 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 5.16.11 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 16, 2024
Action Type Old Value New Value Added Description 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: 1. driver executes its reset_ctrl_work 2. -> nvme_stop_ctrl - flushes ctrl async_event_work 3. ctrl sends AEN which is received by the host, which in turn schedules AEN handling 4. teardown admin queue (which releases the queue socket) 5. AEN processed, submits another AER, calling the driver to submit 6. 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: 1. change ctrl state to RESETTING 2. 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. Added Reference kernel.org https://git.kernel.org/stable/c/a25e460fbb0340488d119fb2e28fe3f829b7417e [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2022-48790
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2022-48790
weaknesses.