CVE-2026-74418

published 15 Aug 2026 · updated 17 Aug 2026

dma-fence: Fix potential tracepoint null pointer dereferences

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4e01fc9a5bc49b04fad403ffa71299b35e132ca8 and Kernel e94b9f01543cc6a83538c2c2cc645a424d3015ca.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=7.1, >=541c8f2468b933acc5d129e84bd264923675a66e <4e01fc9a5bc49b04fad403ffa71299b35e132ca8, >=541c8f2468b933acc5d129e84bd264923675a66e <e94b9f01543cc6a83538c2c2cc645a424d3015ca4e01fc9a5bc49b04fad403ffa71299b35e132ca8, e94b9f01543cc6a83538c2c2cc645a424d3015ca

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-74418 severity on Zeptric[![CVE-2026-74418](https://zeptric.io/badge/cve/CVE-2026-74418.svg)](https://zeptric.io/cve/CVE-2026-74418)