nvmet-fcloop: Check remoteport port_state before calling done callback
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.18, Kernel 6.18.17, Kernel 6.19.7 and 3 more.
In the Linux kernel, the following vulnerability has been resolved: nvmet-fcloop: Check remoteport port_state before calling done callback In nvme_fc_handle_ls_rqst_work, the lsrsp->done callback is only set when remoteport->port_state is FC_OBJSTATE_ONLINE. Otherwise, the nvme_fc_xmt_ls_rsp's LLDD call to lport->ops->xmt_ls_rsp is expected to fail and the nvme-fc transport layer itself will directly call nvme_fc_xmt_ls_rsp_free instead of relying on LLDD's done callback to free the lsrsp resources. Update the fcloop_t2h_xmt_ls_rsp routine to check remoteport->port_state. If online, then lsrsp->done callback will free the lsrsp. Else, return -ENODEV to signal the nvme-fc transport to handle freeing lsrsp.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=6.17.3 <6.18, >=6.18.1 <6.18.17, >=6.19 <6.19.7, =6.18, =7.0, >=10c165af35d225eb033f4edc7fcc699a8d2d533d <dd677d0598387ea623820ab2bd0e029c377445a3, >=10c165af35d225eb033f4edc7fcc699a8d2d533d <f30b95159a53e72529a9ca1667f11cd1970240a7, =2cf857075bcc8e83c4aa5fe7d8f1efd6af51e04e, >=10c165af35d225eb033f4edc7fcc699a8d2d533d <31d3817bcd9e192b30abe3cf4b68f69d48864dd2 | 6.18, 6.18.17, 6.19.7, dd677d0598387ea623820ab2bd0e029c377445a3, f30b95159a53e72529a9ca1667f11cd1970240a7, 31d3817bcd9e192b30abe3cf4b68f69d48864dd2 |
| linux-kernel: Kernel | >=6.17.3 <6.18, >=6.18.0 <6.18.17, >=6.19.0 <6.19.7 | 6.18, 6.18.17, 6.19.7 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket