CVE-2026-93058: drm/msm: Only fini scheduler after successful init
drm/msm: Only fini scheduler after successful init
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.52 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.6 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.6-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1
Event History
Frequently Asked Questions
When can the unsafe teardown path be reached?
It can be reached when msm_ringbuffer_new() encounters an allocation failure or a scheduler setup failure, including drm_sched_init() failing before scheduler initialization completes.
What condition must be present for drm_sched_fini() to be safe?
drm_sched_fini() should be called only if drm_sched_init() returned 0. The fix tracks successful scheduler initialization so partially initialized scheduler state is not torn down.
How can teams determine whether their kernel includes the fix?
Check whether the relevant drm/msm ringbuffer cleanup path records successful scheduler initialization and gates drm_sched_fini() on that status. The provided stable-kernel references identify commits containing the resolution.