7 matches found
CVE-2022-49946
In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Prevent out-of-bounds access The while loop in raspberrypidiscoverclocks 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...
CVE-2022-49946
In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Prevent out-of-bounds access The while loop in raspberrypidiscoverclocks 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...
CVE-2022-49946
In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Prevent out-of-bounds access The while loop in raspberrypidiscoverclocks 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...
CVE-2022-49946 clk: bcm: rpi: Prevent out-of-bounds access
In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Prevent out-of-bounds access The while loop in raspberrypidiscoverclocks 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...
CVE-2022-49946
CVE-2022-49946 affects the Linux kernel component handling Raspberry Pi clocks (clk: bcm: rpi). The vulnerability arises in raspberrypi_discover_clocks() where the loop relies on the last clock element’s id being zero, a property not guaranteed by Videocore firmware, which could lead to an out-of...
CVE-2022-49946 clk: bcm: rpi: Prevent out-of-bounds access
In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Prevent out-of-bounds access The while loop in raspberrypidiscoverclocks 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...
CVE-2022-49946
In the Linux kernel, the following vulnerability has been resolved: clk: bcm: rpi: Prevent out-of-bounds access The while loop in raspberrypidiscoverclocks 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...