Answer in brief
CVE-2024-27435 records a Unknown severity vulnerability in nvme: fix reconnection fail due to reserved tag allocation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ed01fee283a067c72b2d6500046080dbc1bb9dae <149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8 || >=ed01fee283a067c72b2d6500046080dbc1bb9dae <ff2f90f88d78559802466ad1c84ac5bda4416b3a || >=ed01fee283a067c72b2d6500046080dbc1bb9dae <6851778504cdb49431809b4ba061903d5f592c96 || >=ed01fee283a067c72b2d6500046080dbc1bb9dae <262da920896e2f2ab0e3947d9dbee0aa09045818 || >=ed01fee283a067c72b2d6500046080dbc1bb9dae <de105068fead55ed5c07ade75e9c8e7f86a00d1d | 149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8, ff2f90f88d78559802466ad1c84ac5bda4416b3a, 6851778504cdb49431809b4ba061903d5f592c96, 262da920896e2f2ab0e3947d9dbee0aa09045818, de105068fead55ed5c07ade75e9c8e7f86a00d1d |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-27435 records a Unknown severity vulnerability in nvme: fix reconnection fail due to reserved tag allocation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ed01fee283a067c72b2d6500046080dbc1bb9dae <149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8 || >=ed01fee283a067c72b2d6500046080dbc1bb9dae <ff2f90f88d78559802466ad1c84ac5bda4416b3a || >=ed01fee283a067c72b2d6500046080dbc1bb9dae <6851778504cdb49431809b4ba061903d5f592c96 || >=ed01fee283a067c72b2d6500046080dbc1bb9dae <262da920896e2f2ab0e3947d9dbee0aa09045818 || >=ed01fee283a067c72b2d6500046080dbc1bb9dae <de105068fead55ed5c07ade75e9c8e7f86a00d1d | 149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8, ff2f90f88d78559802466ad1c84ac5bda4416b3a, 6851778504cdb49431809b4ba061903d5f592c96, 262da920896e2f2ab0e3947d9dbee0aa09045818, de105068fead55ed5c07ade75e9c8e7f86a00d1d |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.