In the Linux kernel, the following vulnerability has been resolved: tracing: ring-buffer: Fix to check event length before using Check the event length before adding it for accessing next index in rb_read_data_buffer(). Since this function is used for validating possibly broken ring buffers, the length of the event could be broken. In that case, the new event (e + len) can point a wrong address. To avoid invalid memory access at boot, check whether the length of each event is in the possible range before using it.
https://git.kernel.org/stable/c/b4700c089a10f89de3a5149d57f8a58306458982
https://git.kernel.org/stable/c/9eb80e54494ef1efef8a64bec4ffa672c9cf411e
https://git.kernel.org/stable/c/912b0ee248c529a4f45d1e7f568dc1adddbf2a4a
https://git.kernel.org/stable/c/5026010110a5ad2268d8c23e1e286ab7c736f7ac