Commit 361eb853c655 for kernel

commit 361eb853c655288f3b5c8020f6cd95d69ffe6479
Author: Weigang He <geoffreyhe2@gmail.com>
Date:   Mon Jan 19 11:45:42 2026 +0000

    scripts/tracepoint-update: Fix memory leak in add_string() on failure

    When realloc() fails in add_string(), the function returns -1 but leaves
    *vals pointing to the previously allocated memory. This can cause memory
    leaks in callers like make_trace_array() that return on error without
    freeing the partially built array.

    Fix this by freeing *vals and setting it to NULL when realloc() fails.
    This makes the error handling self-contained in add_string() so callers
    don't need to handle cleanup on failure.

    This bug is found by my static analysis tool and my code review.

    Cc: Masami Hiramatsu <mhiramat@kernel.org>
    Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
    Fixes: e30f8e61e2518 ("tracing: Add a tracepoint verification check at build time")
    Link: https://patch.msgid.link/20260119114542.1714405-1-geoffreyhe2@gmail.com
    Signed-off-by: Weigang He <geoffreyhe2@gmail.com>
    Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>

diff --git a/scripts/tracepoint-update.c b/scripts/tracepoint-update.c
index 90046aedc97b..5cf43c0aac89 100644
--- a/scripts/tracepoint-update.c
+++ b/scripts/tracepoint-update.c
@@ -49,6 +49,8 @@ static int add_string(const char *str, const char ***vals, int *count)
 		array = realloc(array, sizeof(char *) * size);
 		if (!array) {
 			fprintf(stderr, "Failed memory allocation\n");
+			free(*vals);
+			*vals = NULL;
 			return -1;
 		}
 		*vals = array;