Linux
drm/msm: RCU-free the scheduler-containing ring and VM objects
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/
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < 0ba7c696eea3af41ac4712197566a7b94eedc637
- >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < d81bf4581903b0cba0698cd4d1c07fc6be21754a
- >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < 713abac5c04ccbae67f9ac68c3921845535388e7
- >= 1d8a5ca436ee4a28eec14cb813f790f7cdeeee19, < 01c8d1f385f788f1bbbbb7687c4386d614281218
Fixed in 0ba7c696eea3af41ac4712197566a7b94eedc637, d81bf4581903b0cba0698cd4d1c07fc6be21754a, 713abac5c04ccbae67f9ac68c3921845535388e7, 01c8d1f385f788f1bbbbb7687c4386d614281218
- 5.15
Fixed in 0, 6.12.117, 6.18.54, 7.2.8, 7.3
Mitigation
Upgrade Linux to 0ba7c696eea3af41ac4712197566a7b94eedc637 or d81bf4581903b0cba0698cd4d1c07fc6be21754a or 713abac5c04ccbae67f9ac68c3921845535388e7 or 01c8d1f385f788f1bbbbb7687c4386d614281218 or later.
Upgrade Linux to 0 or 6.12.117 or 6.18.54 or 7.2.8 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.1 informational
Informational 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| MalHyuk/CVE-2026-98180 | 18 Oct 2026 +12 d | 14 Nov 2026 | 0 | Informational · detection
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.