LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can leave NVMe-over-RDMA storage unable to reconnect after a controller reset, even when the target and network are healthy. The result is an availability failure that may persist indefinitely, potentially disrupting storage-dependent applications. The supplied assessment rates it CVSS 7.5 because availability can be severely affected; confidentiality and integrity are not impacted.

Executive priority

Prioritize remediation for business-critical hosts whose applications depend on NVMe-over-RDMA storage. Treat this as a resilience and outage risk rather than a data-theft issue. Accelerate action where controller resets, network instability, or storage-path recovery events are operationally plausible.

Technical view

During NVMe-over-Fabrics reconnection, the admin and fabric queues share a tag set. A keep-alive request can retain the only reserved tag while the admin queue is quiesced, preventing the reconnect command from obtaining a tag. This ABBA-style deadlock blocks admin-queue recovery. The kernel fix retains two reserved admin-queue tags.

Likely exposure

Exposure is concentrated in Linux systems using NVMe over RDMA, particularly where controller resets or reconnection events occur. Systems not using this storage path are unlikely to encounter the described failure. The supplied version data is not sufficiently structured to establish exact distribution package boundaries, so vendor-specific kernel advisories should determine applicability.

Exploitation context

The supplied sources describe a production-observed availability failure, not a demonstrated attack. CVE-2024-27435 is not listed as KEV in the bundle, and no cited evidence establishes active exploitation or public weaponization. Although the supplied CVSS vector is network-based, the source description does not prove that an unauthenticated remote party can deliberately trigger the condition.

Researcher notes

The reported root cause is reserved-tag starvation across shared admin and fabric queue resources during reset recovery. The change increases reserved admin-queue tags to two. Exact affected and fixed package versions require distribution confirmation; the bundle lists kernel versions and five stable commits but does not provide an unambiguous version-to-fix mapping.

Mitigation direction

  • Identify Linux hosts using NVMe over RDMA and prioritize storage-critical systems.
  • Apply a vendor-supported kernel containing the relevant stable fix.
  • Use distribution guidance to map packaged kernels to CVE-2024-27435.
  • Schedule controlled storage failover or maintenance before updating production hosts.

Validation and detection

  • Confirm whether each host uses NVMe over RDMA.
  • Compare installed kernel packages with vendor CVE guidance and fixed builds.
  • Review storage and kernel telemetry for persistent admin-queue reconnection failures.
  • After updating, test controller reset and reconnection in an authorized maintenance window.
  • Verify applications regain storage access without repeated recovery failures.
Prepared
Confidence
high
Sources
7

Public sources used

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-2024-27435 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-27435Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxed01fee283a067c72b2d6500046080dbc1bb9dae, ed01fee283a067c72b2d6500046080dbc1bb9dae, ed01fee283a067c72b2d6500046080dbc1bb9dae, ed01fee283a067c72b2d6500046080dbc1bb9dae, ed01fee283a067c72b2d6500046080dbc1bb9daeunaffected
LinuxLinux5.12, 0, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.