scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 78a582463c1e3a262aeaf2a291e06a93a7b34212 · < 09a60f908d8b6497f618113b7c3c31267dc90911| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: fcoe: Fix transport not deattached when fcoe_if_init() fails
fcoe_init() calls fcoe_transport_attach(&fcoe_sw_transport), but when fcoe_if_init() fails, &fcoe_sw_transport is not detached and leaves freed &fcoe_sw_transport on fcoe_transports list. This causes panic when reinserting module.
BUG: unable to handle page fault for address: fffffbfff82e2213 RIP: 0010:fcoe_transport_attach+0xe1/0x230 [libfcoe] Call Trace: <TASK> do_one_initcall+0xd0/0x4e0 load_module+0x5eee/0x7210 ...
From the CVE record · Linux
In the Linux kernel, a failed fcoe_if_init() leaves a freed transport on the transport list. Reinserting the module after that failure can cause a kernel panic; the input does not specify authentication requirements.
Engineers running Linux kernels that use the FCoE module should check their installations; affected versions are not specified.