CVE-2022-48790

published 16 Jul 2024 · updated 5 Aug 2026

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

9.8CriticalCVSS 9.8EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 0ead57ceb21bbf15963b4874c2ac67143455382f, Kernel 0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d, Kernel 70356b756a58704e5c8818cb09da5854af87e765 and 3 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.15, >=ad22c355b707a8d8d48e282aadc01c0b0604b2e9 <0ead57ceb21bbf15963b4874c2ac67143455382f, >=ad22c355b707a8d8d48e282aadc01c0b0604b2e9 <0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d, >=ad22c355b707a8d8d48e282aadc01c0b0604b2e9 <70356b756a58704e5c8818cb09da5854af87e765, >=ad22c355b707a8d8d48e282aadc01c0b0604b2e9 <9e956a2596ae276124ef0d96829c013dd0faf861, >=ad22c355b707a8d8d48e282aadc01c0b0604b2e9 <a25e460fbb0340488d119fb2e28fe3f829b7417e, >=ad22c355b707a8d8d48e282aadc01c0b0604b2e9 <e043fb5a0336ee74614e26f0d9f36f1f5bb6d6060ead57ceb21bbf15963b4874c2ac67143455382f, 0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d, 70356b756a58704e5c8818cb09da5854af87e765, 9e956a2596ae276124ef0d96829c013dd0faf861, a25e460fbb0340488d119fb2e28fe3f829b7417e, e043fb5a0336ee74614e26f0d9f36f1f5bb6d606

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-48790 severity on Zeptric[![CVE-2022-48790](https://zeptric.io/badge/cve/CVE-2022-48790.svg)](https://zeptric.io/cve/CVE-2022-48790)