What is CVE-2026-98180?

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

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

CVE-2026-98180 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-98180?

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

Is CVE-2026-98180 actively exploited?

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

CVE-2026-98180

High

In the Linux kernel, the following vulnerability has been resolved: drm/msm: RCU-free the scheduler-containing ring and VM objects Both struct msm_ringbuffer and struct msm_gem_vm embed a struct drm_gpu_scheduler. msm_ringbuffer_destroy() and the VM free callback msm_gem_vm_free() call drm_sched_fini() on the embedded scheduler and then free the containing object with plain kfree(). drm_sched_fence_get_timeline_name() returns fence->sched->name, and the scheduler fence keeps a .release callback so it is not ops-detached on signalling. A finished fence exported to userspace (the submit out-fence, or a VM_BIND fence, via sync_file / drm_syncobj) keeps pointing at the embedded scheduler after the ring/VM is freed, so a later get_timeline_name() -- reachable unprivileged through SYNC_IOC_FILE_INFO -- dereferences freed slab memory (KASAN slab-use-after-free read). Per the dma-fence lifetime contract the exporter must keep the data backing a signalled fence alive for an RCU grace period. Free the scheduler-containing objects with kfree_rcu() instead of kfree(). Patchwork: https://patchwork.freedesktop.org/patch/750234/

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 5.15 and later are affected. Fixed in 6.18.54, 7.2.8, 7.3-rc4 and their respective stable series.

Affected from

≥ 5.15

Fixed in

✓ 6.18.54 6.18.x ✓ 7.2.8 7.2.x ✓ 7.3-rc4

References

3 total

Details

CVE ID CVE-2026-98180

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-98180?

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

CVE-2026-98180 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-98180?

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

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