VulnerabilityPublished 17 May 2024Updated 8 Oct 2026

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

Affects Linux kernelSource GCVE Database

Not known to be exploited · CVSS 7.5 High · fixed in 6.8.0-35.35 : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.8.0-35.35, 6.8.0-1009.9, 6.8.0-1008.8 +7

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Patches and advisories

Affected software

Product	Affected	Fixed in
Ubuntu 24.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=noble`Other threats	Affected <6.8.0-35.35	Fixed in 6.8.0-35.35
Ubuntu 24.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=noble`Other threats	Affected <6.8.0-1009.9	Fixed in 6.8.0-1009.9
Ubuntu 24.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=noble`Other threats	Affected <6.8.0-1008.8	Fixed in 6.8.0-1008.8
Ubuntu 24.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=noble`Other threats	Affected <6.8.0-1008.9	Fixed in 6.8.0-1008.9
Ubuntu 24.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=noble`Other threats	Affected <6.8.0-1004.7	Fixed in 6.8.0-1004.7
Ubuntu 24.04 LTSlinux-ibm`pkg:deb/ubuntu/linux-ibm?arch=source&distro=noble`Other threats	Affected <6.8.0-1006.6	Fixed in 6.8.0-1006.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

An official patch is available and should be applied to affected Linux kernel versions to resolve the issue. The patch increases the number of reserved tags for the admin queue to prevent the deadlock. Users should update to patched kernel versions as per vendor advisories. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel NVMe driver related to reserved tag allocation has been fixed. The issue caused the admin queue to fail to reconnect when using NVMe over RDMA due to a deadlock involving tag allocation between admin and fabric queues. This could result in a permanent failure to reconnect the admin queue, impacting availability. The vulnerability has a CVSS score of 7.5 and is considered to have a high impact on availability but no confidentiality or integrity impact. A patch is available to address this issue by reserving two tags for the admin queue to avoid deadlock.

Impact

The vulnerability leads to a denial of service condition by causing the NVMe admin queue to fail reconnecting permanently during NVMe over RDMA operations. This impacts system availability but does not affect confidentiality or integrity. There is no indication of remote code execution or privilege escalation. No known exploits are reported in the wild.

Summary

CVE-2024-27435 describes a Linux kernel vulnerability in the NVMe driver where the admin queue (admin_q) fails to reconnect over NVMe over RDMA due to a deadlock caused by reserved tag allocation. The deadlock occurs because a reserved tag is held by a keep-alive request waiting inside the admin queue, which is quiesced during controller reset. Since the fabric queue shares the tagset with the admin queue, the reconnect command cannot obtain a reserved tag, causing the admin queue to fail reconnecting indefinitely. The fix involves reserving two tags for the admin queue to prevent this deadlock scenario.

References

Community reviews

Loading reviews…