remoteproc: imx_rproc: Fix invalid loaded resource table detection
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e954a1bd16102abc800629f9900715d8ec4c3130 · < 198c629bd03863591f3fbf5ce8ff974a33f13dc9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
remoteproc: imx_rproc: Fix invalid loaded resource table detection
imx_rproc_elf_find_loaded_rsc_table() may incorrectly report a loaded resource table even when the current firmware does not provide one.
When the device tree contains a "rsc-table" entry, priv->rsc_table is non-NULL and denotes where a resource table would be located if one is present in memory. However, when the current firmware has no resource table, rproc->table_ptr is NULL. The function still returns priv->rsc_table, and the remoteproc core interprets this as a valid loaded resource table.
Fix this by returning NULL from imx_rproc_elf_find_loaded_rsc_table() when there is no resource table for the current firmware (i.e. when rproc->table_ptr is NULL). This aligns the function's semantics with the remoteproc core: a loaded resource table is only reported when a valid table_ptr exists.
With this change, starting firmware without a resource table no longer triggers a crash.
From the CVE record · Linux
The Linux kernel's imx_rproc component can incorrectly report a loaded resource table when the device tree has an "rsc-table" entry but the current firmware has no resource table. Starting that firmware can trigger a crash. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels that use the imx_rproc component should check their systems; affected versions are not specified.