{"id":"CVE-2026-98243","title":"In the Linux kernel, the following vulnerability has been resolved:\n\ndma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3\n\nThe patch \"dma-buf: dma-fence: Fix potential NULL pointer dereference\"\nchanged the check …","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\ndma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3\n\nThe patch \"dma-buf: dma-fence: Fix potential NULL pointer dereference\"\nchanged the check …","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 035219a760edb35ae9a9e96beba7f122e26a997b < a4db25b8949d6ff9c1a685a1273a015e8bab29db","Linux >= 035219a760edb35ae9a9e96beba7f122e26a997b < 3ed11c671ff7ec58c8fd96410233c677df23f407","Linux 15ecfdf0ef6f6d874d0a26690d300857b39ebfd0","Linux >= 7.1.5 < 7.2","Linux 7.2"],"published":"2026-10-06","updated":"2026-10-06","sourceUpdated":"2026-10-06T09:18:12.383","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-98243","references":[{"url":"https://git.kernel.org/stable/c/3ed11c671ff7ec58c8fd96410233c677df23f407","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/a4db25b8949d6ff9c1a685a1273a015e8bab29db","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-10-06T08:50:17.433Z","slug":"CVE-2026-98243","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndma-buf/dma-fence: fix checking signaling bit for timeline and driver name v3\n\nThe patch \"dma-buf: dma-fence: Fix potential NULL pointer dereference\"\nchanged the check to test for the ops pointer instead of the signaled\nbit to avoid a potential NULL dereference when the ops pointer has been\ncleared.\n\nThe problem is now that the ops pointer is cleared only when neither the\nrelease nor the wait callback is implemented and this isn't true for a lot\nof dma_fence implementations yet. So those implementations lost the RCU\nprotection after signaling of the returned string resulting in potential\nuse after free.\n\nAdd the signaling check additional to the ops pointer check so that we\nhave both the protection against NULL dereference as well as the RCU\nprotection after signaling for the returned string.\n\nv2: improve comments to note RCU protection and explain why we check\n    both signaling state and ops pointer\nv3: some comment improvements suggested by Philip\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}