# CVE-2024-27435: nvme: fix reconnection fail due to reserved tag allocation

> A deadlock in the Linux kernel NVMe driver prevents reconnection, causing a denial of service for NVMe over RDMA connections.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 17 May 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-67581, BELL-CVE-2024-27435, DEBIAN-CVE-2024-27435, GHSA-5mwv-x2qc-g5cj, ROOT-OS-UBUNTU-2204-CVE-2024-27435, UBUNTU-CVE-2024-27435

## What is CVE-2024-27435?

CVE-2024-27435 is a high-severity vulnerability in Linux kernel, published on 17 May 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: fix reconnection fail due to reserved tag allocation

We found a issue on production environment while using NVMe over RDMA,
admin_q reconnect failed forever while remote target and network is ok.
After dig into it, we found it may caused by a ABBA deadlock due to tag
allocation. In my case, the tag was hold by a keep alive request
waiting inside admin_q, as we quiesced admin_q while reset ctrl, so the
request maked as idle and will not process before reset success. As
fabric_q shares tagset with admin_q, while reconnect remote target, we
need a tag for connect command, but the only one reserved tag was held
by keep alive command which waiting inside admin_q. As a result, we
failed to reconnect admin_q forever. In order to fix this issue, I
think we should keep two reserved tags for admin queue.

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2024-27435?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-27435?

Apply the vendor's patch.

## Is CVE-2024-27435 being exploited?

There is no known exploitation of CVE-2024-27435 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-2024-27435 and fix it if it is affected.

What it is: CVE-2024-27435 is a high-severity vulnerability in Linux kernel, published on 17 May 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-2024-27435 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-2024-27435/ (Markdown: https://insights.sbomify.com/CVE-2024-27435/index.md)
```

## Sources

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

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