CVE-2022-48788: nvme-rdma: fix possible use-after-free in transport error_recovery work
In the Linux kernel, the following vulnerability has been resolved:
nvme-rdma: fix possible use-after-free in transport error_recovery work
While nvme_rdma_submit_async_event_work is checking the ctrl and queue
state before preparing the AER command and scheduling io_work, in order
to fully prevent a race where this check is not reliable the error
recovery work must flush async_event_work before continuing to destroy
the admin queue after setting the ctrl state to RESETTING such that
there is no race .submit_async_event and the error recovery handler
itself changing the ctrl state.
Security readout for executives and security teams
Plain-English summary
CVE-2022-48788 is a Linux kernel flaw in the NVMe over RDMA storage transport. A race during error recovery could leave work running against a destroyed admin queue, creating a possible use-after-free. Business urgency depends on whether affected Linux kernels use NVMe over RDMA in production storage paths.
Executive priority
Set a focused remediation track for Linux storage infrastructure using NVMe over RDMA. Broader emergency response is not supported by the provided evidence because severity, exploitability, and active exploitation are not documented.
Technical view
The issue is in nvme-rdma error recovery. The fix flushes async_event_work after setting the controller state to RESETTING and before destroying the admin queue, preventing a race between async event submission and error recovery state changes. Public sources do not provide CVSS, CWE, privilege requirements, or a demonstrated impact beyond possible use-after-free.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with NVMe over RDMA enabled or used. General Linux hosts without this storage transport are less likely to be reachable through this bug, based on the provided description.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. No public exploit status, attack prerequisites, or real-world incident details are provided. Treat exploitation likelihood as unconfirmed rather than absent.
Researcher notes
Useful evidence is limited to the CVE record and Linux stable commit references. The key behavior is a race in async event work versus error recovery queue destruction. Further analysis should inspect vendor backports and local kernel configurations, not assume remote exploitability.
Mitigation direction
Apply Linux kernel stable fixes or distribution updates containing the referenced commits.
Prioritize systems using NVMe over RDMA for production storage.
Check Linux distribution advisories for backported fixes and supported kernel versions.
Avoid unsupported kernels where fixed stable updates are unavailable.
Validation and detection
Inventory Linux kernel versions across servers and storage nodes.
Identify systems using the nvme-rdma transport.
Compare installed kernels with vendor-fixed versions or referenced stable commits.
Confirm patch status through distribution package metadata or kernel changelogs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48788 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.