Overview
About vulnerability
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. A flaw was found in the Linux kernel’s tracing ring-buffer subsystem. This vulnerability occurs in therb_read_data_buffer() function, which fails to validate the length of an event before using it to determine the next memory address. If an event’s length is corrupted, this can lead to an invalid memory access during system boot, potentially causing a denial of service (DoS) by crashing the system.
Details
KernelCare state
Live-patch status from KernelCare for each operating system.
| Operating system | Status | Covered kernels |
|---|---|---|
| Debian 13 | Planned | — |