nvme-fc: use lock accessing port_state and rport state
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e399441de9115cd472b8ace6c517708273ca7997 · < a2f7fa75c4a2a07328fa22ccbef461db76790b55| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's nvme-fc code has a race between remote-port removal and reconnection when no association is active. The input does not specify what an attacker could achieve or whether network access, authentication, or user interaction is required.
Engineers running Linux kernel versions with the affected nvme-fc code should check their systems; affected versions are not specified.