CVE-2022-48789: nvme-tcp: fix possible use-after-free in transport error_recovery work
In the Linux kernel, the following vulnerability has been resolved:
nvme-tcp: fix possible use-after-free in transport error_recovery work
While nvme_tcp_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
A race in Linux NVMe-over-TCP error recovery can let asynchronous work access an admin queue after it is being destroyed. This use-after-free may cause memory corruption or system failure. Risk is concentrated in systems using the Linux NVMe/TCP transport.
Executive priority
Treat affected NVMe/TCP storage hosts as urgent because kernel memory-safety failures can disrupt critical storage services. Prioritize confirmation and patching, especially where NVMe/TCP crosses less-trusted networks. Systems not using NVMe/TCP should receive lower priority after validation.
Technical view
The error-recovery worker changed the controller state and destroyed the admin queue without first flushing pending async-event work. A concurrent asynchronous-event submission could therefore use freed queue memory. The stable fixes flush async_event_work before queue teardown, closing the race.
Likely exposure
Potential exposure is limited to Linux systems using NVMe over TCP. The bundle associates affected status with kernel lines from 5.0 through 5.17 and lists several stable versions, but its version data is ambiguous. Distribution backports must be checked individually.
Exploitation context
The supplied CVSS is 9.8 and models unauthenticated network attack potential with high impact. However, the source bundle provides no proof of practical exploitation, public weaponization, or active exploitation, and the CVE is not marked as CISA KEV.
Researcher notes
The vulnerable condition is a teardown race between async-event submission and transport error recovery. Source material identifies the ordering fix but does not establish exploitability beyond the CVSS assessment. The flattened affected-version list contains unclear entries, including โ0,โ so upstream commits and distribution advisories are stronger validation anchors.
Mitigation direction
Update to a vendor-supported kernel containing the applicable nvme-tcp stable fix.
Confirm the selected distribution package includes the relevant upstream backport.
If updating is delayed, assess whether NVMe/TCP can be safely disabled or isolated.
Monitor Linux and distribution advisories for corrected version guidance.
Validation and detection
Inventory systems loading or using the Linux nvme-tcp transport.
Record running kernel and distribution package versions on exposed systems.
Compare vendor backport records against the referenced stable kernel commits.
After updating, confirm the corrected kernel is running following any required reboot.
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-48789 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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.