---
id: CVE-2026-98180
title: |-
  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
summary: |-
  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_destr…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 <
    d81bf4581903b0cba0698cd4d1c07fc6be21754a
  - >-
    Linux >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 <
    713abac5c04ccbae67f9ac68c3921845535388e7
  - >-
    Linux >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19 <
    01c8d1f385f788f1bbbbb7687c4386d614281218
  - Linux 5.15
published: '2026-10-06'
updated: '2026-10-06'
sourceUpdated: '2026-10-06T09:18:01.617'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-98180'
references:
  - url: 'https://git.kernel.org/stable/c/01c8d1f385f788f1bbbbb7687c4386d614281218'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/713abac5c04ccbae67f9ac68c3921845535388e7'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/d81bf4581903b0cba0698cd4d1c07fc6be21754a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-10-06T08:50:17.452Z'
---

## Overview

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/

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.