Description
In the Linux kernel, the following vulnerability has been resolved:

dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3

The patch "dma-buf: dma-fence: Fix potential NULL pointer dereference"
changed the check to test for the ops pointer instead of the signaled
bit to avoid a potential NULL dereference when the ops pointer has been
cleared.

The problem is now that the ops pointer is cleared only when neither the
release nor the wait callback is implemented and this isn't true for a lot
of dma_fence implementations yet. So those implementations lost the RCU
protection after signaling of the returned string resulting in potential
use after free.

Add the signaling check additional to the ops pointer check so that we
have both the protection against NULL dereference as well as the RCU
protection after signaling for the returned string.

v2: improve comments to note RCU protection and explain why we check
both signaling state and ops pointer
v3: some comment improvements suggested by Philip
Published: 2026-10-06
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Use After Free (potential NULL pointer dereference)
Action: Patch Immediately
AI Analysis

Impact

A flaw in the Linux kernel’s DMA fence implementation allows the ops pointer to be cleared after a fence is signaled without sufficient RCU protection, which can lead to a use‑after‑free or NULL pointer dereference when the ops pointer is accessed. The vulnerability resides in the kernel’s handling of DMA fence objects and can compromise kernel integrity if triggered by a DMA fence operation. The root cause is the improper check that tests the ops pointer instead of the signalling bit, allowing the ops pointer to be cleared prematurely for many implementations.

Affected Systems

All Linux kernel binaries that employ the default DMA fence implementation prior to the patch are potentially affected. No specific version numbers are listed in the advisory, so any kernel build using the relevant dma‑buf/dma‑fence code before the latest change is susceptible.

Risk and Exploitability

The EPSS score is < 1% and KEV is not listed; a CVSS score of 7.1 is assigned. The vulnerability can result in a kernel use‑after‑free, which typically carries a high severity level. Although specific exploitation probability metrics are absent, the theoretical impact remains significant if the flaw is triggered during DMA fence handling. The patch restores RCU protection and prevents the use‑after‑free condition.

Generated by OpenCVE AI on October 11, 2026 at 16:32 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch that adds the missing signalling check in the dma‑fence code; the patch can be retrieved from the provided git references and applied to the source before compiling.
  • Upgrade the system to a Linux kernel version that incorporates this fix; most recent stable releases contain the corrected implementation.
  • If an immediate kernel upgrade is not feasible, temporarily disable or safely remove any DMA driver that does not implement both release and wait callbacks to prevent ops pointer clearance until the kernel can be patched or the driver updated.

Generated by OpenCVE AI on October 11, 2026 at 16:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 11 Oct 2026 12:15:00 +0000


Wed, 07 Oct 2026 09:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-476

Wed, 07 Oct 2026 07:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

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


Tue, 06 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-476

Tue, 06 Oct 2026 09:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3 The patch "dma-buf: dma-fence: Fix potential NULL pointer dereference" changed the check to test for the ops pointer instead of the signaled bit to avoid a potential NULL dereference when the ops pointer has been cleared. The problem is now that the ops pointer is cleared only when neither the release nor the wait callback is implemented and this isn't true for a lot of dma_fence implementations yet. So those implementations lost the RCU protection after signaling of the returned string resulting in potential use after free. Add the signaling check additional to the ops pointer check so that we have both the protection against NULL dereference as well as the RCU protection after signaling for the returned string. v2: improve comments to note RCU protection and explain why we check both signaling state and ops pointer v3: some comment improvements suggested by Philip
Title dma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3
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-10-19T09:16:14.740Z

Reserved: 2026-09-25T10:25:14.330Z

Link: CVE-2026-98243

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-06T09:18:12.383

Modified: 2026-10-19T10:18:25.193

Link: CVE-2026-98243

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-06T00:00:00Z

Links: CVE-2026-98243 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-11T16:45:06Z

Weaknesses
  • CWE-825

    Expired Pointer Dereference