KernelScan.io

HIGH Introduced in 5.15

drm/msm SchedFence UAF

CVE-2026-98180

CVSS 7.1 / 10.0 NVD

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

KernelScan AI7.8HIGH

01

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/

02

Engine v0.7.0

Risk summary

An unprivileged local user with access to a Qualcomm Adreno (MSM) DRM device node can trigger a use-after-free read in the kernel by exporting a GPU fence to userspace, destroying the underlying ringbuffer or VM object, and then querying the fence timeline name. This can lead to kernel memory disclosure, memory corruption, or a system crash. Systems without MSM GPU hardware are not affected.

Affecteddrivers/gpu/drm/msm/msm_ringbuffer.c, msm_gem_vma.c (MSM DRM GPU driver)

Vulnerability analysis

The MSM DRM driver frees ringbuffer and virtual-memory objects that embed a GPU scheduler too early, before a userspace-exported fence has stopped referencing them. When an unprivileged user later queries that fence's timeline name through a standard sync-file ioctl, the kernel reads from already-freed memory. The fix defers freeing these scheduler-containing objects with RCU, ensuring the memory remains valid for a grace period after teardown. The vulnerability is reachable by any unprivileged local user with access to the MSM DRM render device node — typically available on systems with Qualcomm Adreno GPU hardware.

03

BranchIntroducedFixed inPatch commit
6.125.156.12.1170ba7c696eea3
6.185.156.18.54d81bf4581903
7.25.157.2.8713abac5c04c
mainline5.157.301c8d1f385f7

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Affected — no CIP fix yet (latest 6.12.114-cip34)
cip/6.1Affected — no CIP fix yet (latest 6.1.190-cip62)
cip/6.1-rtAffected — no CIP fix yet (latest 6.1.189-cip61-rt32)