nvmet-fc: avoid scheduling association deletion twice
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.
CVE-2025-40343
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2025-40343
Linux
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Linux
Source reference: /containers/cna/affected/1/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "a07b4970f464f13640e28e16dad6cfa33647cc99",
"lessThan": "2f4852db87e25d4e226b25cb6f652fef9504360e",
"versionType": "git"
},
{
"status": "affected",
"version": "a07b4970f464f13640e28e16dad6cfa33647cc99",
"lessThan": "85e2ce1920cb511d57aae59f0df6ff85b28bf04d",
"versionType": "git"
},
{
"status": "affected",
"version": "a07b4970f464f13640e28e16dad6cfa33647cc99",
"lessThan": "601ed47b2363c24d948d7bac0c23abc8bd459570",
"versionType": "git"
},
{
"status": "affected",
"version": "a07b4970f464f13640e28e16dad6cfa33647cc99",
"lessThan": "04d17540ef51e2c291eb863ca87fd332259b2d40",
"versionType": "git"
},
{
"status": "affected",
"version": "a07b4970f464f13640e28e16dad6cfa33647cc99",
"lessThan": "c09ac9a63fc3aaf4670ad7b5e4f5afd764424154",
"versionType": "git"
},
{
"status": "affected",
"version": "a07b4970f464f13640e28e16dad6cfa33647cc99",
"lessThan": "f2537be4f8421f6495edfa0bc284d722f253841d",
"versionType": "git"
}
],
"programFiles": [
"drivers/nvme/target/fc.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "4.8"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "4.8",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.15.197",
"versionType": "semver",
"lessThanOrEqual": "5.15.*"
},
{
"status": "unaffected",
"version": "6.1.159",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.6.117",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.58",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.17.8",
"versionType": "semver",
"lessThanOrEqual": "6.17.*"
},
{
"status": "unaffected",
"version": "6.18",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/nvme/target/fc.c"
],
"defaultStatus": "affected"
}
]- Related CVEs
- CVE-2025-40343
Source reference:
/cveMetadata/cveId
Publisher severity
critical
Source reference: /containers/cna/metrics
- Event
- #30719 · Revision 1
- Added to Heist Feed
- Publisher date