PCI: brcmstb: Fix error path after a call to regulator_bulk_get()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9e6be018b26347c26a93e63fb50a37ee2c9311de · < 3651ad5249c51cf7eee078e12612557040a6bdb4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
PCI: brcmstb: Fix error path after a call to regulator_bulk_get()
If the regulator_bulk_get() returns an error and no regulators are created, we need to set their number to zero.
If we don't do this and the PCIe link up fails, a call to the regulator_bulk_free() will result in a kernel panic.
While at it, print the error value, as we cannot return an error upwards as the kernel will WARN() on an error from add_bus().
[kwilczynski: commit log, use comma in the message to match style with other similar messages]
From the CVE record · Linux
The Linux kernel brcmstb PCIe driver can panic if regulator_bulk_get() fails without creating regulators and the PCIe link subsequently fails to come up. The input does not establish how an attacker could trigger this condition, or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the brcmstb PCIe driver should check their exposure; affected versions were not provided.