nvmet-fc: move lsop put work to nvmet_fc_ls_req_op
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 710c69dbaccdac312e32931abcb8499c1525d397 · < db5a5406fb7e5337a074385c7a3e53c77f2c1bd3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvmet-fc: move lsop put work to nvmet_fc_ls_req_op
It’s possible for more than one async command to be in flight from __nvmet_fc_send_ls_req. For each command, a tgtport reference is taken.
In the current code, only one put work item is queued at a time, which results in a leaked reference.
To fix this, move the work item to the nvmet_fc_ls_req_op struct, which already tracks all resources related to the command.
From the CVE record · Linux
The Linux kernel's nvmet-fc code can leak a target-port reference when more than one asynchronous command is in flight from __nvmet_fc_send_ls_req. The input does not specify how an attacker could trigger this condition or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with nvmet-fc should check their versions; affected versions are not specified.