Answer in brief
CVE-2024-41082 records a Unknown severity vulnerability in nvme-fabrics: use reserved tag for reg read/write command. 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 | >=e7832cb48a654cd12b2bc9181b2f0ad49d526ac6 <cc91c461cf3902993364ea85d8814ba7786c95b1 || >=e7832cb48a654cd12b2bc9181b2f0ad49d526ac6 <165da9c67a26f08c9b956c15d701da7690f45bcb || >=e7832cb48a654cd12b2bc9181b2f0ad49d526ac6 <7dc3bfcb4c9cc58970fff6aaa48172cb224d85aa | cc91c461cf3902993364ea85d8814ba7786c95b1, 165da9c67a26f08c9b956c15d701da7690f45bcb, 7dc3bfcb4c9cc58970fff6aaa48172cb224d85aa |
| Linux/Linuxgeneric | 5.4 | Not reported |
Published upstream
Jul 29, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 3, 2026
In the Linux kernel, the following vulnerability has been resolved: nvme-fabrics: use reserved tag for reg read/write command In some scenarios, if too many commands are issued by nvme command in the same time by user tasks, this may exhaust all tags of admin_q. If a reset (nvme reset or IO timeout) occurs before these commands finish, reconnect routine may fail to update nvme regs due to insufficient tags, which will cause kernel hang forever. In order to workaround this issue, maybe we can let reg_read32()/reg_read64()/reg_write32() use reserved tags. This maybe safe for nvmf: 1. For the disable ctrl path, we will not issue connect command 2. For the enable ctrl / fw activate path, since connect and reg_xx() are called serially. So the reserved tags may still be enough while reg_xx() use reserved tags.
Quoted source text, attributed separately from HOL analysis.