Linux Kernel trace_probe nr_args Limit Fix Preventing NULL Pointer Dereference

From this webpage screenshot, we can extract the following key information about the vulnerability: 1. Vulnerability Description: - When creating a trace_probe, is set, but during probe setup, only up to 128 arguments are initialized. - This leads to invalid memory access when attempting to set the probe if more than 128 arguments are provided. 2. Error Information: - Kernel NULL pointer access at address 0000000000000020. - Error code 0x0000 — not in kernel mode. - Error code 0x0000 — not in kernel mode. - Error code 0x0000 — not in kernel mode. 3. Hardware Information: - CPU: 0 UID: 0 PID: 1769. - Memory: . - Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-1.fc39 04/01/2014. 4. Resolution: - The issue is resolved by applying the limit earlier during probe setup. - When arguments exceed the limit, an error is returned instead of silently truncating. 5. Patch Content: - Modified function to return error code when arguments exceed . - Modified , , and functions to return error code when arguments exceed . 6. Patch Application: - This patch fixes the issue in , correcting the initialization of during . - The patch was submitted by Mikel Rychliski and Masami Hiramatsu. This information indicates that the vulnerability is related to the creation functions in the kernel. When more than arguments are provided, it causes invalid memory access. The issue is resolved by enforcing the limit earlier during probe setup and returning an error instead of silently truncating.

Goal Reached Thanks to every supporter — we hit 100%!

Linux Kernel trace_probe nr_args Limit Fix Preventing NULL Pointer Dereference