CVE-2025-40342
nvme-fc: use lock accessing port_state and rport state
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing port_state and rport state nvme_fc_unregister_remote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reconnect logic, because nvme_fc_create_association is not taking a lock to check the port_state and atomically increase the active count on the rport.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.10
References 7
git.kernel.org
- stable/c/de3d91af47bc015031e7721b100a29989f6498a5
- stable/c/e8cde03de8674b05f2c5e0870729049eba517800
- stable/c/4253e0a4546138a2bf9cb6acf66b32fee677fc7c
- stable/c/25f4bf1f7979a7871974fd36c79d69ff1cf4b446
- stable/c/9950af4303942081dc8c7a5fdc3688c17c7eb6c0
- stable/c/a2f7fa75c4a2a07328fa22ccbef461db76790b55
- stable/c/891cdbb162ccdb079cd5228ae43bdeebce8597ad