soc: ti: pruss: Fix double free in pruss_clk_mux_setup()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ba59c9b43c86b2c2396acac94e41d946cbaec9fe · < b7db9953c2f8da37de498198623b05b46f8e2ca0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
soc: ti: pruss: Fix double free in pruss_clk_mux_setup()
In the pruss_clk_mux_setup(), the devm_add_action_or_reset() indirectly calls pruss_of_free_clk_provider(), which calls of_node_put(clk_mux_np) on the error path. However, after the devm_add_action_or_reset() returns, the of_node_put(clk_mux_np) is called again, causing a double free.
Fix by returning directly, to avoid the duplicate of_node_put().
From the CVE record · Linux
The Linux kernel’s PRUSS clock mux setup can release the same device-tree node twice when an error occurs. The input does not specify what an attacker could do or whether triggering the error requires local access, authentication, or user interaction.
Engineers running Linux kernels with the TI PRUSS component should check their versions; affected versions were not provided.