CVE-2024-27435 Details
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.
A deadlock vulnerability has been identified in the Linux kernel's NVMe over RDMA implementation. This issue arises during the reconnection process of the admin queue, which can fail indefinitely due to a reserved tag allocation conflict. The problem occurs when a keep-alive request in the admin queue holds a reserved tag, preventing the allocation of a new tag needed for the reconnection command. As a result, the admin queue fails to reconnect, causing a persistent disruption. This vulnerability affects the Linux kernel's stable releases.
The vulnerability has been addressed by modifying the NVMe tag allocation process. The admin queue now retains two reserved tags to prevent such deadlock scenarios. Users should update to the latest version of the Linux kernel where this fix has been applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 31, 2024References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.12.1, < 6.1.83 >= 6.2, < 6.6.23 >= 6.7, < 6.7.11 >= 6.8, < 6.8.2 5.12 - 5.12 rc4 5.12 rc5 5.12 rc6 5.12 rc7 5.12 rc8 |
CPE
Remediation
| |
Change History
9 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Sep 26, 2025 | Reanalysis | [email protected] |
| Sep 19, 2025 | Initial Analysis | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| Nov 6, 2024 | CVE Modified | CISA-ADP |
| May 29, 2024 | CVE Modified | kernel.org |
| May 17, 2024 | New CVE Received | kernel.org |