CVE-2022-48790
Last modified
CVE-2022-48790 is a high-severity vulnerability rated 7/10 on the CVSS scale. 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. EPSS estimates a 0.26% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 4.19.231 |
| Linux | Linux Kernel | >= 4.20, < 5.4.181 |
| Linux | Linux Kernel | >= 5.5, < 5.10.102 |
| Linux | Linux Kernel | >= 5.11, < 5.15.25 |
| Linux | Linux Kernel | >= 5.16, < 5.16.11 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-48790?
How severe is CVE-2022-48790?
How do I fix CVE-2022-48790?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-48785In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48786In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48787In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-48788In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-48789In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-4879A vulnerability was found in Forged Alliance Forever up to 3…7.5
- CVE-2022-48791In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-48792In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-48793In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48794In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48795In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-48796In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2022-48790?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
