# CVE-2022-48788: nvme-rdma: fix possible use-after-free in transport error_recovery work

> A race condition in the Linux kernel's NVMe RDMA driver can lead to a use-after-free, potentially allowing local attackers to execute code or escalate privileges.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-47446, DEBIAN-CVE-2022-48788, GHSA-grc2-v3f8-wj3j, UBUNTU-CVE-2022-48788

## What is CVE-2022-48788?

CVE-2022-48788 is a critical use after free vulnerability in Linux kernel, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2022-48788?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2022-48788?

Apply the vendor's patch.

## Is CVE-2022-48788 being exploited?

There is no known exploitation of CVE-2022-48788 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48788 and fix it if it is affected.

What it is: CVE-2022-48788 is a critical use after free vulnerability in Linux kernel, published on 16 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48788 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48788/ (Markdown: https://insights.sbomify.com/CVE-2022-48788/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48788
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48788
- OSV: https://osv.dev/vulnerability/CVE-2022-48788

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48788/
Summaries are generated and may contain mistakes; the official description above is the record.