CVE-2022-48790

Advisory lineage Upstream: 0 Downstream: 14
Modified
Published: 16 Jul 2024, 11:43
Last modified:11 May 2026, 18:47

Vulnerability Summary

Overall Risk (default)
medium
28/100
CVSS Score
7 HIGH
v3.1 (nvd)
EPSS Score
0.02% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

16 Jul 2024, 11:43
Published
Vulnerability first disclosed
11 May 2026, 18:47
Last Modified
Vulnerability information updated

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.

CVSS Metrics

  • v3.1•HIGH•Score: 7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 0.02%• Percentile: 4%

Techniques & Countermeasures

  • CWE-416•Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

  • linux•linux

    ≥ ad22c355b707a8d8d48e282aadc01c0b0604b2e9, < a25e460fbb0340488d119fb2e28fe3f829b7417e | ≥ ad22c355b707a8d8d48e282aadc01c0b0604b2e9, < 70356b756a58704e5c8818cb09da5854af87e765 | ≥ ad22c355b707a8d8d48e282aadc01c0b0604b2e9, < 0ead57ceb21bbf15963b4874c2ac67143455382f | ≥ ad22c355b707a8d8d48e282aadc01c0b0604b2e9, < e043fb5a0336ee74614e26f0d9f36f1f5bb6d606 | ≥ ad22c355b707a8d8d48e282aadc01c0b0604b2e9, < 9e956a2596ae276124ef0d96829c013dd0faf861 | ≥ ad22c355b707a8d8d48e282aadc01c0b0604b2e9, < 0fa0f99fc84e41057cbdd2efbfe91c6b2f47dd9d | 4.15

  • linux•linux_kernel

    < 4.19.231 | ≥ 4.20, < 5.4.181 | ≥ 5.5, < 5.10.102 | ≥ 5.11, < 5.15.25 | ≥ 5.16, < 5.16.11

References (6)