Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98180 Overview
CVE-2026-98180 is a use-after-free vulnerability in the Linux kernel's Qualcomm MSM Direct Rendering Manager (drm/msm) driver. The flaw resides in the handling of struct msm_ringbuffer and struct msm_gem_vm, both of which embed a struct drm_gpu_scheduler. When msm_ringbuffer_destroy() and the VM free callback msm_gem_vm_free() call drm_sched_fini() and then release the containing object with kfree(), exported fences continue referencing freed scheduler memory. An unprivileged local user can trigger the dangling dereference through the SYNC_IOC_FILE_INFO ioctl, producing a KASAN slab-use-after-free read.
Critical Impact
A local unprivileged user with access to a graphics device node on an affected MSM GPU platform can trigger kernel memory corruption, leading to potential denial of service or privilege escalation.
Affected Products
- Linux kernel builds including the drm/msm driver (Qualcomm Adreno GPU support)
- Devices and distributions shipping affected kernel revisions prior to the fix commits
- Downstream vendor kernels that inherit the pre-patch msm_ringbuffer and msm_gem_vm lifetime handling
Discovery Timeline
- 2026-10-06 - CVE-2026-98180 published to the National Vulnerability Database
- 2026-10-07 - Entry last modified in NVD
Technical Details for CVE-2026-98180
Vulnerability Analysis
The drm/msm driver embeds a drm_gpu_scheduler directly inside both msm_ringbuffer and msm_gem_vm. When these containers are destroyed, the driver calls drm_sched_fini() on the embedded scheduler and immediately frees the enclosing object with kfree(). This violates the dma-fence lifetime contract, which requires the exporter to keep data backing a signalled fence alive for at least one RCU grace period.
Scheduler fences retain a .release callback and therefore are not ops-detached on signalling. The function drm_sched_fence_get_timeline_name() returns fence->sched->name, meaning any fence exported to user space continues to point into the freed scheduler. Submit out-fences and VM_BIND fences delivered via sync_file or drm_syncobj extend the window during which stale pointers can be dereferenced.
Root Cause
The root cause is improper object lifetime management for scheduler-containing structures. Freeing with plain kfree() does not honor the RCU-protected read side used by fence timeline accessors, producing a classic use-after-free condition in slab-allocated kernel memory.
Attack Vector
Exploitation requires local access and the ability to open the DRM render node and submit GPU work. After obtaining a fence file descriptor from a submit or VM_BIND operation, an attacker triggers destruction of the owning ring or VM, then calls SYNC_IOC_FILE_INFO on the retained fence. The ioctl path invokes drm_sched_fence_get_timeline_name(), which dereferences the freed scheduler object. See the upstream fix in Kernel Git Commit 713abac for the corrected teardown sequence.
Detection Methods for CVE-2026-98180
Indicators of Compromise
- KASAN reports in dmesg containing slab-use-after-free with call stacks referencing drm_sched_fence_get_timeline_name or sync_file_ioctl
- Kernel oops or general protection faults originating from msm_ringbuffer_destroy or msm_gem_vm_free code paths
- Unexpected process crashes or GPU driver resets following SYNC_IOC_FILE_INFO activity by unprivileged processes
Detection Strategies
- Enable KASAN on test kernels to surface the use-after-free during fuzzing of DRM ioctls
- Correlate kernel crash telemetry with processes holding fence file descriptors obtained from /dev/dri/renderD*
- Audit syscall traces for sequences of GPU submit operations followed by SYNC_IOC_FILE_INFO against released contexts
Monitoring Recommendations
- Forward kernel ring buffer and kdump output to a centralized log store for anomaly review
- Alert on repeated DRM driver faults or GPU scheduler teardown errors on fleet endpoints
- Monitor loaded kernel versions across the environment to flag hosts still running pre-patch builds
How to Mitigate CVE-2026-98180
Immediate Actions Required
- Inventory Linux hosts running the drm/msm driver, particularly Qualcomm-based mobile, embedded, and laptop platforms
- Apply vendor kernel updates incorporating the upstream fix as soon as they are available
- Restrict access to DRM render nodes to trusted local users where feasible
Patch Information
The fix replaces kfree() with kfree_rcu() for the scheduler-containing msm_ringbuffer and msm_gem_vm objects, ensuring an RCU grace period elapses before memory is reclaimed. Reference commits: Kernel Git Commit 01c8d1f, Kernel Git Commit 713abac, and Kernel Git Commit d81bf45. Deploy distribution kernel packages that include these backports.
Workarounds
- Limit DRM device node permissions via udev rules so only authorized accounts can open /dev/dri/renderD*
- Disable or avoid workloads that export GPU fences to user space via sync_file or drm_syncobj on unpatched systems
- Where supported, run untrusted graphical workloads inside sandboxed sessions with reduced syscall surface
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

