CVE Catalog

CVE-2026-98243

HighCVSS 7.1
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.12%

2th percentile - higher than 2% of all known CVEs

Summary

In the Linux kernel dma-buf/dma-fence module, a previous fix changed the signaling check to an ops pointer check, causing loss of RCU protection after signaling for many dma_fence implementations, leading to use-after-free. The fix adds an additional signaling check alongside the ops pointer check.

Risk Assessment

Use-after-free may lead to system crashes or potential kernel code execution, posing a serious security risk.

Recommendation

Apply a Linux kernel update containing the fix for dma-fence signaling and ops pointer checks.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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

Vulnerability data from NVD (NIST) · CISA KEV · EPSS