clk: bcm: rpi: Prevent out-of-bounds access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
clk: bcm: rpi: Prevent out-of-bounds access
The while loop in raspberrypi_discover_clocks() relies on the assumption that the id of the last clock element is zero. Because this data comes from the Videocore firmware and it doesn't guarantuee such a behavior this could lead to out-of-bounds access. So fix this by providing a sentinel element.
From the CVE record · Linux
The Linux kernel’s raspberrypi_discover_clocks() function assumes the last clock ID supplied by Videocore firmware is zero, but the firmware does not guarantee this. If that assumption fails, the function can access data out of bounds. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the Raspberry Pi clock discovery code should check their installations; affected versions are not specified.