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.
Published: 2026-08-15
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel contains a race condition that allows tracepoint callbacks—specifically trace_dma_fence_signaled, trace_dma_fence_wait_end, and trace_dma_fence_destroy—to dereference a null fence->ops pointer after a fence has been reset during signalling. This null‑pointer dereference can crash the kernel, resulting in a denial of service for the affected system. The vulnerability is a classic Null Pointer Dereference (CWE‑476).

Affected Systems

All Linux kernel vendors are potentially impacted, as the issue is part of the core kernel source. The affected versions are those containing the unpatched dma‑fence tracepoint code; no specific version range is listed, so any release lacking the commit 4e01fc9a5bc49b04fad403ffa71299b35e132ca8 is vulnerable.

Risk and Exploitability

The CVSS score is 5.5, and the EPSS score is less than 1%, but the problem is not listed in CISA’s KEV catalog. The likely attack vector is local kernel access, such as a privileged process or kernel module that triggers the offending tracepoints. A successful exploit would cause a kernel panic or loss of service rather than remote code execution. The risk is moderate for environments where local privilege escalation is achievable or where untrusted drivers can be loaded.

Generated by OpenCVE AI on August 21, 2026 at 22:30 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a release that includes the dma‑fence tracepoint null dereference fix (commit 4e01fc9a5bc49b04fad403ffa71299b35e132ca8).
  • If a kernel upgrade cannot be performed immediately, disable the tracepoints that may dereference a null ops pointer—trace_dma_fence_signaled, trace_dma_fence_wait_end, and trace_dma_fence_destroy—to prevent the crash.
  • Review any custom kernel modules or drivers that use dma_fence tracepoints and add null‑pointer checks before accessing fence->ops to avoid the vulnerable code path.

Generated by OpenCVE AI on August 21, 2026 at 22:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 21 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Sat, 15 Aug 2026 14:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476

Sat, 15 Aug 2026 06:15:00 +0000

Type Values Removed Values Added
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.
Title dma-fence: Fix potential tracepoint null pointer dereferences
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:19:01.013Z

Reserved: 2026-08-15T05:44:03.893Z

Link: CVE-2026-74418

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:22:43.907

Modified: 2026-08-17T06:19:37.283

Link: CVE-2026-74418

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-74418 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-21T22:45:04Z

Weaknesses