Answer in brief
CVE-2025-40343 records a Critical severity (CVSS 9.8) vulnerability in nvmet-fc: avoid scheduling association deletion twice. 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.
CVSS is 9.8. 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 | >=a07b4970f464f13640e28e16dad6cfa33647cc99 <2f4852db87e25d4e226b25cb6f652fef9504360e || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <85e2ce1920cb511d57aae59f0df6ff85b28bf04d || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <601ed47b2363c24d948d7bac0c23abc8bd459570 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <04d17540ef51e2c291eb863ca87fd332259b2d40 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <c09ac9a63fc3aaf4670ad7b5e4f5afd764424154 || >=a07b4970f464f13640e28e16dad6cfa33647cc99 <f2537be4f8421f6495edfa0bc284d722f253841d | 2f4852db87e25d4e226b25cb6f652fef9504360e, 85e2ce1920cb511d57aae59f0df6ff85b28bf04d, 601ed47b2363c24d948d7bac0c23abc8bd459570, 04d17540ef51e2c291eb863ca87fd332259b2d40, c09ac9a63fc3aaf4670ad7b5e4f5afd764424154, f2537be4f8421f6495edfa0bc284d722f253841d |
| Linux/Linuxgeneric | 4.8 | Not reported |
Published upstream
Dec 9, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid scheduling association deletion twice When forcefully shutting down a port via the configfs interface, nvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and then nvmet_disable_port(). Both functions will eventually schedule all remaining associations for deletion. The current implementation checks whether an association is about to be removed, but only after the work item has already been scheduled. As a result, it is possible for the first scheduled work item to free all resources, and then for the same work item to be scheduled again for deletion. Because the association list is an RCU list, it is not possible to take a lock and remove the list entry directly, so it cannot be looked up again. Instead, a flag (terminating) must be used to determine whether the association is already in the process of being deleted.
Quoted source text, attributed separately from HOL analysis.