CVE-2026-74418
Last modified
CVE-2026-74418 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 541c8f2468b933acc5d129e84bd264923675a66e, < 4e01fc9a5bc49b04fad403ffa71299b35e132ca8; >= 541c8f2468b933acc5d129e84bd264923675a66e, < e94b9f01543cc6a83538c2c2cc645a424d3015ca |
| Linux | Linux | 7.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74418?
How severe is CVE-2026-74418?
How do I fix CVE-2026-74418?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74412In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-74413In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-74414In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74415In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74416In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74417In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74419In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-74420In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74421In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74422In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74423In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74424In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-74418?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
