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 A1C3C3876C7 for ; Sat, 15 Aug 2026 06:39:58 +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=1786775999; cv=none; b=ps7nWmQeAciz0C/35gsMbh8razIhmGnrXwTgEp2PeQmgAjZBVyST4jRjP6mY45FAxT6qgDBU5MhX0LxbG9857HfN3z+aQPLcJ6A8Igrb09BXvrshA02JACDcoALO3YMkrspTk6eJj5tH3nvxr0HQ6th56KXC8FDxmGVFxfuPkSo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786775999; c=relaxed/simple; bh=VsRxdLO6SQ0smdp/4dzm5iWt+MYa85TTrwfTo+KaqjM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=mfJfsWhyzH9XYB/mKlv5LLvr4PEQQTBo/0YQRBLQhlnDhD7LPyrbSXE8+TenA8Xa05ys5Tfux6sLVFKqbLjkC6lIPDiAInhjpCCNJZS8fargj3xCSzkvhfs3UZyk/Yszd1rvu+aNoLmOdnUOCfxXq3GiqtFiiJhS+3NXiAd5lmY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=w943eow4; 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="w943eow4" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C2D931F00A3A; Sat, 15 Aug 2026 06:39:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786775998; bh=VJ1R62rrL4c2PiJwyB34MUsgwuWuczzNa2752bKBkBk=; h=From:To:Cc:Subject:Date:Reply-To; b=w943eow4k5I8kcSAc+w/ieKgTV4gRLzDzYtPLagGW30DJzq8UoOcRBKS8Gj/OMGHq ASifB1tVFIseCzfEVr+stJXCu/NRulduF9szBoUxfeZHPZB2FAUBYF23+8T8Ok1Lep fpkQuMjuZKYSzN8YIxhIBly4lVoLMenNCbRfMmW8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74418: dma-fence: Fix potential tracepoint null pointer dereferences Date: Sat, 15 Aug 2026 15:12:25 +0900 Message-ID: <2026081512-CVE-2026-74418-0a40@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=2632; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=qr5nWPu23oXk5P15yN/3DlXmEVCctgwxHC6rgioSr2Q=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNjApZz837pv0VTr2cdtKsn1WMbZGLtquAK/de/m1sr /+n75fsiGVhEGRikBVTZPmyjefo/opDil6Gtqdh5rAygQxh4OIUgIksDWWYKybRVu39tf1mcpCK 6cH272Jzdy2rYpjNcih+X/FesV1ZjAWrC3ecjir777McAA== 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: dma-fence: Fix potential tracepoint null pointer dereferences Trace_dma_fence_signaled, trace_dma_fence_wait_end and trace_dma_fence_destroy can all currently dereference a null fence->ops pointer after it has been reset on fence signalling. Lets use the safe string getters for most tracepoints to avoid this class of a problem, while for the signal tracepoint we move it to before ops are cleared to avoid losing the driver and timeline name information. Apart from moving it we also need to add a new tracepoint class to bypass the safe name getters since the signaled bit is already set. For dma_fence_init we also need to use the new tracepoint class since the rcu read lock is not held there, and we can do the same for the enable signaling since there we are certain the fence cannot be signaled while we are holding the lock and have even validated the fence->ops. The Linux kernel CVE team has assigned CVE-2026-74418 to this issue. Affected and fixed versions =========================== Issue introduced in 7.1 with commit 541c8f2468b933acc5d129e84bd264923675a66e and fixed in 7.1.5 with commit 4e01fc9a5bc49b04fad403ffa71299b35e132ca8 Issue introduced in 7.1 with commit 541c8f2468b933acc5d129e84bd264923675a66e and fixed in 7.2-rc1 with commit e94b9f01543cc6a83538c2c2cc645a424d3015ca 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-74418 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: drivers/dma-buf/dma-fence.c include/trace/events/dma_fence.h 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/4e01fc9a5bc49b04fad403ffa71299b35e132ca8 https://git.kernel.org/stable/c/e94b9f01543cc6a83538c2c2cc645a424d3015ca