CVE-2026-98180

drm/msm: RCU-free the scheduler-containing ring and VM objects

Published Oct 6, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
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/

Analysis

AI-generated

Technical impact

The Linux kernel contains a use‑after‑free vulnerability in the msm DRM driver. The driver frees scheduler‑containing ring buffers or VM objects with a plain kfree() instead of kfree_rcu(). When a fence that references the embedded scheduler is still in use, a later call to drm_sched_fence_get_timeline_name() dereferences freed slab memory, allowing an attacker to read or corrupt sensitive kernel data.

Affected Systems

All systems running a Linux kernel that includes the drm/msm component are affected. No specific kernel version range is listed, but the problem is fixed in recent releases by replacing kfree() with kfree_rcu() in msm_ringbuffer_destroy() and msm_gem_vm_free().

Risk and Exploitability

The attacker only needs local unprivileged access and can trigger the flaw by sending a SYNC_IOC_FILE_INFO ioctl with a fence exported via sync_file or drm_syncobj. The EPSS score is less than 1%, and the vulnerability is not in CISA KEV, but the CVSS score of 7.1 and the possibility of kernel memory corruption suggest a high risk of privilege escalation or denial of service if exploited.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that contains the kfree_rcu patch for msm_ringbuffer_destroy() and msm_gem_vm_free(); for example, install updates that include commit 01c8d1f or later.
  • If the required update is not available in your distribution, backport the kfree_rcu change from the referenced commit into your kernel source tree and rebuild the kernel.
  • Apply device permission restrictions or udev rules to limit unprivileged access to DRM sync objects, reducing the likelihood of an attacker invoking the vulnerable SYNC_IOC_FILE_INFO ioctl.

Generated by OpenCVE AI on October 9, 2026 at 04:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9160-1 Linux kernel (Azure) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Description 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/
Title drm/msm: RCU-free the scheduler-containing ring and VM objects
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-825

    Expired Pointer Dereference

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 10, 2026, 6:15 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 6, 2026, 9:18 AM
Modified
Nov 10, 2026, 7:22 PM
Severity
Moderate
Public date
Oct 6, 2026, 12:00 AM