From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 00F263EA970 for ; Sat, 15 Aug 2026 12:28:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786796929; cv=none; b=W1Qq5y3w4g77YnF5Suhgfy9sbX7YmAuyifJJhboG2G8jcpHvw68e/HC8TH1OaBV1P+cv9JT5B5eg8mGqNCeUyM6RTmXCjTGRdLM81R73xRGkmSGjRWN7GDvun/lLAYUJNZRzkshlh2mrhPF30VdpY+ZjHs9rT0V4qjhy1PAln24= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786796929; c=relaxed/simple; bh=CYZsqYJ9aqgB4DIONZ5dz+PnoYgIsE0AxWrxGwWJFBk=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=JJChamvtOILZDsW0eYo0QfJBJVEsB+aj2jFxj5ly2EkdV0A0ByDOZE4j7bLjM55SiSDwoT59dJsfEUBUsLofRMiD2jtjsOGzeapsjGbkJ5W6Xx925kIYFStQW/3uNn4/byETYWXyIgwaHywPH5ZO9gZUdaAsWvQh5xFjOmrkiZo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=bpSfD0rU; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="bpSfD0rU" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5AC801F000E9; Sat, 15 Aug 2026 12:28:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786796927; bh=A6tCwJwmk0lPFwxrEkFtT3quGcdQwk2FbGnCe4bFSbQ=; h=From:To:Cc:Subject:Date:Reply-To; b=bpSfD0rUpYVgaM/QcyHUBqRWCsso9PqaSkjbUxu/BS82Q58qu4rKo6HM9W2ubFSQR TjC64xH2TsE3SYuqjB38QzUdpoXknAzTkTpDIgNn9H8C+V2lFP6tqM7OBgYe27F1ij qtiIiZAlG9x4d6op3XbAxLKien6Ak0Yzbs2W80Q4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74471: tracing: Check return value of __register_event() in trace_module_add_events() Date: Sat, 15 Aug 2026 21:25:52 +0900 Message-ID: <2026081534-CVE-2026-74471-5629@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3202; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=M6NCRVVXTkMU4tM93pupGyqJxa+wgxgv/siJ7FzbQoQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNUfuWNR72W2W4NKxkFdtsq5kM/EyXzF4tnXQrNDSJ9 edlD66nHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRtGqGBfNvl7+8sLNlX/D6 pfNkD9ysWLw/+ijDXPnMxBdtb9d6xHuYJuY8rPgoNVXnBAA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: tracing: Check return value of __register_event() in trace_module_add_events() trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event. If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed. Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded. The Linux kernel CVE team has assigned CVE-2026-74471 to this issue. Affected and fixed versions =========================== Issue introduced in 3.10 with commit ae63b31e4d0e2ec09c569306ea46f664508ef717 and fixed in 6.6.151 with commit d61ee2a27dfd5eb43ddc18af40168f5b9eb1cea5 Issue introduced in 3.10 with commit ae63b31e4d0e2ec09c569306ea46f664508ef717 and fixed in 6.12.103 with commit 22f954f7a8afe975e85517aff41b35defe05144b Issue introduced in 3.10 with commit ae63b31e4d0e2ec09c569306ea46f664508ef717 and fixed in 6.18.44 with commit cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca Issue introduced in 3.10 with commit ae63b31e4d0e2ec09c569306ea46f664508ef717 and fixed in 7.1.8 with commit 000765dcdc3edf128990762790543adc4b868f6c Issue introduced in 3.10 with commit ae63b31e4d0e2ec09c569306ea46f664508ef717 and fixed in 7.2-rc6 with commit ac8719969e6c3c54e939834df812bc41f25453cf Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-74471 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: kernel/trace/trace_events.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/d61ee2a27dfd5eb43ddc18af40168f5b9eb1cea5 https://git.kernel.org/stable/c/22f954f7a8afe975e85517aff41b35defe05144b https://git.kernel.org/stable/c/cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca https://git.kernel.org/stable/c/000765dcdc3edf128990762790543adc4b868f6c https://git.kernel.org/stable/c/ac8719969e6c3c54e939834df812bc41f25453cf