What is CVE-2026-98243?

CVE-2026-98243 is a High severity Linux kernel vulnerability with a CVSS score of 7.1 out of 10, affecting Linux kernel versions from 7.1.5 onward and patched in 7.2.8 and 7.3-rc4. CVE-2026-98243 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-98243?

CVE-2026-98243 has a CVSS score of 7.1 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H.

Is there a patch available for CVE-2026-98243?

Yes, CVE-2026-98243 has been patched. Fixed versions include 7.2.8 and 7.3-rc4. If you are running Linux kernel 7.1.5 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-98243 actively exploited?

CVE-2026-98243 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-98243

High

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

Package Linux Kernel

Published 2026-10-06

Last modified 2026-10-07

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.1

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Affected versions

Linux kernel versions 7.1.5, 7.2 and later are affected. Fixed in 7.2.8, 7.3-rc4 and their respective stable series.

Affected from

≥ 7.1.5 ≥ 7.2

Fixed in

✓ 7.2.8 7.2.x ✓ 7.3-rc4

References

2 total

Details

CVE ID CVE-2026-98243

Severity High

CVSS score 7.1 / 10

CVSS version 3.1

Published 2026-10-06

Modified 2026-10-07

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-98243?

CVE-2026-98243 is a High severity Linux kernel vulnerability with a CVSS score of 7.1 out of 10 . It affects Linux kernel versions from 7.1.5 onward and has been patched in 7.2.8 and 7.3-rc4. CVE-2026-98243 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-98243?

CVE-2026-98243 has a CVSS score of 7.1 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H.
Is there a patch available for CVE-2026-98243?

Yes. CVE-2026-98243 has been patched. Fixed versions include 7.2.8 and 7.3-rc4. If you are running Linux kernel 7.1.5 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-98243 actively exploited?

No. CVE-2026-98243 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.