CVE-2022-48790

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.
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

History

21 Nov 2024, 07:34

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f - Patch () https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f - Patch
References () https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d - Patch () https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d - Patch
References () https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765 - Patch () https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765 - Patch
References () https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861 - Patch () https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861 - Patch
References () https://git.kernel.org/stable/c/a25e460fbb0340488d119fb2e28fe3f829b7417e - Patch () https://git.kernel.org/stable/c/a25e460fbb0340488d119fb2e28fe3f829b7417e - Patch
References () https://git.kernel.org/stable/c/e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 - Patch () https://git.kernel.org/stable/c/e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 - Patch

07 Aug 2024, 20:06

Type Values Removed Values Added
CWE CWE-416
First Time Linux
Linux linux Kernel
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 7.0
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
References () https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f - () https://git.kernel.org/stable/c/0ead57ceb21bbf15963b4874c2ac67143455382f - Patch
References () https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d - () https://git.kernel.org/stable/c/0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d - Patch
References () https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765 - () https://git.kernel.org/stable/c/70356b756a58704e5c8818cb09da5854af87e765 - Patch
References () https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861 - () https://git.kernel.org/stable/c/9e956a2596ae276124ef0d96829c013dd0faf861 - Patch
References () https://git.kernel.org/stable/c/a25e460fbb0340488d119fb2e28fe3f829b7417e - () https://git.kernel.org/stable/c/a25e460fbb0340488d119fb2e28fe3f829b7417e - Patch
References () https://git.kernel.org/stable/c/e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 - () https://git.kernel.org/stable/c/e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 - Patch
Summary
  • (es) En el kernel de Linux, se resolvió la siguiente vulnerabilidad: nvme: corrige un posible use-after-free en el reinicio del controlador durante la carga. A diferencia de .queue_rq, en .submit_async_event es posible que los controladores no verifiquen la preparación de Ctrl para el envío de AER. Esto puede provocar una condición de use-after-free que se observó con nvme-tcp. La condición de ejecución puede ocurrir en el siguiente escenario: 1. el controlador ejecuta su reset_ctrl_work 2. -> nvme_stop_ctrl - vacía ctrl async_event_work 3. ctrl envía AEN que es recibido por el host, que a su vez programa el manejo de AEN 4. desmontaje de la cola de administración (que libera el socket de la cola) 5. AEN procesado, envía otro AER, llamando al controlador para enviar 6. el controlador intenta enviar el cmd ==> use-after-free Para solucionar eso, agregue la verificación de estado de ctrl para validar que ctrl es realmente capaz de aceptar la presentación de la ARE. Esto soluciona la ejecución anterior en los reinicios del controlador porque el controlador durante el desmontaje debe: 1. cambiar el estado de Ctrl a RESTABLECER 2. vaciar async_event_work (así como otros elementos de trabajo asíncronos) Entonces, después de 1,2, cualquier otro comando AER encontrará el estado de Ctrl estar RESETING y rescatar sin presentar la AER.

16 Jul 2024, 12:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-07-16 12:15

Updated : 2024-11-21 07:34


NVD link : CVE-2022-48790

Mitre link : CVE-2022-48790

CVE.ORG link : CVE-2022-48790


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-416

Use After Free