remoteproc: k3-r5: Fix error handling when power-up failed
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
8ae2a10f5c7010ac82ab015cf864199093d61a7d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: k3-r5: Fix error handling when power-up failed
By simply bailing out, the driver was violating its rule and internal assumptions that either both or no rproc should be initialized. E.g., this could cause the first core to be available but not the second one, leading to crashes on its shutdown later on while trying to dereference that second instance.
From the CVE record · Linux
The Linux kernel’s remoteproc k3-r5 driver can leave one core initialized when power-up of another fails. A later shutdown can crash when the driver dereferences the uninitialized instance; the input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels that use the remoteproc k3-r5 driver should check their kernel versions; affected versions are not specified.