nvmet-fc: avoid scheduling association deletion twice
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 04d17540ef51e2c291eb863ca87fd332259b2d40, Kernel 2f4852db87e25d4e226b25cb6f652fef9504360e, Kernel 601ed47b2363c24d948d7bac0c23abc8bd459570 and 3 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.8, >=a07b4970f464f13640e28e16dad6cfa33647cc99 <04d17540ef51e2c291eb863ca87fd332259b2d40, >=a07b4970f464f13640e28e16dad6cfa33647cc99 <2f4852db87e25d4e226b25cb6f652fef9504360e, >=a07b4970f464f13640e28e16dad6cfa33647cc99 <601ed47b2363c24d948d7bac0c23abc8bd459570, >=a07b4970f464f13640e28e16dad6cfa33647cc99 <85e2ce1920cb511d57aae59f0df6ff85b28bf04d, >=a07b4970f464f13640e28e16dad6cfa33647cc99 <c09ac9a63fc3aaf4670ad7b5e4f5afd764424154, >=a07b4970f464f13640e28e16dad6cfa33647cc99 <f2537be4f8421f6495edfa0bc284d722f253841d | 04d17540ef51e2c291eb863ca87fd332259b2d40, 2f4852db87e25d4e226b25cb6f652fef9504360e, 601ed47b2363c24d948d7bac0c23abc8bd459570, 85e2ce1920cb511d57aae59f0df6ff85b28bf04d, c09ac9a63fc3aaf4670ad7b5e4f5afd764424154, f2537be4f8421f6495edfa0bc284d722f253841d |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket