scsi: lpfc: Inhibit aborts if external loopback plug is inserted
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a1516930cb605caee3bc7b4f3b7994b88c0b8505 and Kernel ead76d4c09b89f4c8d632648026a476a5a34fde8.
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Inhibit aborts if external loopback plug is inserted After running a short external loopback test, when the external loopback is removed and a normal cable inserted that is directly connected to a target device, the system oops in the llpfc_set_rrq_active() routine. When the loopback was inserted an FLOGI was transmit. As we're looped back, we receive the FLOGI request. The FLOGI is ABTS'd as we recognize the same wppn thus understand it's a loopback. However, as the ABTS sends address information the port is not set to (fffffe), the ABTS is dropped on the wire. A short 1 frame loopback test is run and completes before the ABTS times out. The looback is unplugged and the new cable plugged in, and the an FLOGI to the new device occurs and completes. Due to a mixup in ref counting the completion of the new FLOGI releases the fabric ndlp. Then the original ABTS completes and references the released ndlp generating the oops. Correct by no-op'ing the ABTS when in loopback mode (it will be dropped anyway). Added a flag to track the mode to recognize when it should be no-op'd.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.3, >=1b51197d0fd0c06877c6df1bba84ac4008a7fc60 <a1516930cb605caee3bc7b4f3b7994b88c0b8505, >=1b51197d0fd0c06877c6df1bba84ac4008a7fc60 <ead76d4c09b89f4c8d632648026a476a5a34fde8 | a1516930cb605caee3bc7b4f3b7994b88c0b8505, ead76d4c09b89f4c8d632648026a476a5a34fde8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket