{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-98180","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.322Z","datePublished":"2026-10-06T08:44:23.327Z","dateUpdated":"2026-10-07T06:49:28.231Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-10-07T06:49:28.231Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm: RCU-free the scheduler-containing ring and VM objects\n\nBoth struct msm_ringbuffer and struct msm_gem_vm embed a struct\ndrm_gpu_scheduler.  msm_ringbuffer_destroy() and the VM free callback\nmsm_gem_vm_free() call drm_sched_fini() on the embedded scheduler and then\nfree the containing object with plain kfree().\n\ndrm_sched_fence_get_timeline_name() returns fence->sched->name, and the\nscheduler fence keeps a .release callback so it is not ops-detached on\nsignalling.  A finished fence exported to userspace (the submit out-fence, or\na VM_BIND fence, via sync_file / drm_syncobj) keeps pointing at the embedded\nscheduler after the ring/VM is freed, so a later get_timeline_name() --\nreachable unprivileged through SYNC_IOC_FILE_INFO -- dereferences freed slab\nmemory (KASAN slab-use-after-free read).\n\nPer the dma-fence lifetime contract the exporter must keep the data backing a\nsignalled fence alive for an RCU grace period.  Free the scheduler-containing\nobjects with kfree_rcu() instead of kfree().\n\nPatchwork: https://patchwork.freedesktop.org/patch/750234/"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","baseScore":7.1,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The freed memory is reached by a local process through render-node ioctls (MSM_SET_PARAM to enable VM_BIND, MSM_VM_BIND/MSM_GEM_SUBMIT with an out-fence) followed by SYNC_IOC_FILE_INFO on the exported sync_file. No remote data is involved.\nAC:L - The attacker runs every step: create a user-managed VM, submit a VM_BIND job with an out-fence fd, close the DRM fd so msm_gem_vm_close()/msm_gem_vm_free() kfree the VM, then query the sync_file. They choose when the free happens, so there is no race they can't control.\nPR:L - All msm ioctls used are DRM_RENDER_ALLOW and the sync_file ioctl needs only the fd. An unprivileged user with render-node access (render group, or any Android app with GPU access) can do this without capabilities.\nUI:N - No victim action is needed. The attacker creates and frees the VM and queries the fence entirely through their own file descriptors.\nS:U - This is a use-after-free in the kernel's own memory with impact inside the same kernel authority. No VM, IOMMU or sandbox boundary is crossed.\nC:H - drm_sched_fence_get_timeline_name() returns fence->sched->name from the freed msm_gem_vm. If the slab is refilled with attacker data, that name pointer is attacker-controlled, and sync_fill_fence_info() strscpy()s up to 32 bytes from that address into obj_name returned to userspace. That is a repeatable arbitrary kernel read.\nI:N - Nothing writes through the stale fence->sched: get_timeline_name only reads it and sched_entity.c only compares the pointer. The freed scheduler gives a read primitive, not a write or control-flow primitive.\nA:H - Dereferencing freed or reclaimed memory and strscpy() from a bad name pointer causes a kernel oops/panic (KASAN slab-use-after-free read), which the attacker can trigger repeatedly."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/msm/msm_gem.h","drivers/gpu/drm/msm/msm_gem_vma.c","drivers/gpu/drm/msm/msm_ringbuffer.c","drivers/gpu/drm/msm/msm_ringbuffer.h"],"versions":[{"version":"1d8a5ca436ee4a28eec14cb813f790f7cdeeee19","lessThan":"d81bf4581903b0cba0698cd4d1c07fc6be21754a","status":"affected","versionType":"git"},{"version":"1d8a5ca436ee4a28eec14cb813f790f7cdeeee19","lessThan":"713abac5c04ccbae67f9ac68c3921845535388e7","status":"affected","versionType":"git"},{"version":"1d8a5ca436ee4a28eec14cb813f790f7cdeeee19","lessThan":"01c8d1f385f788f1bbbbb7687c4386d614281218","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/msm/msm_gem.h","drivers/gpu/drm/msm/msm_gem_vma.c","drivers/gpu/drm/msm/msm_ringbuffer.c","drivers/gpu/drm/msm/msm_ringbuffer.h"],"versions":[{"version":"5.15","status":"affected"},{"version":"0","lessThan":"5.15","status":"unaffected","versionType":"semver"},{"version":"6.18.54","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.2.8","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3-rc4","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"6.18.54"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"7.2.8"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"7.3-rc4"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/d81bf4581903b0cba0698cd4d1c07fc6be21754a"},{"url":"https://git.kernel.org/stable/c/713abac5c04ccbae67f9ac68c3921845535388e7"},{"url":"https://git.kernel.org/stable/c/01c8d1f385f788f1bbbbb7687c4386d614281218"}],"title":"drm/msm: RCU-free the scheduler-containing ring and VM objects","x_generator":{"engine":"bippy-1.2.0"}}}}