CVE-2026-93183

drm/lima: call drm_mm_init() with a valid allocation range

N/A
Published: September 17, 2026 at 04:12 PM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/lima: call drm_mm_init() with a valid allocation range lima_vm_create() is currently run before va_start and va_end are set up, meaning they are both 0. lima_vm_create() runs drm_mm_init() with them as arguments for the allocator, and if DRM_DEBUG_MM is enabled the DRM_MM_BUG_ON check in drm_mm_init then fires, as seen here on exynos4412-odroid-u2: [ 1.736297] ------------[ cut here ]------------ [ 1.740370] kernel BUG at drivers/gpu/drm/drm_mm.c:931! [ 1.745574] Internal error: Oops - BUG: 0 [#1] SMP ARM [ 1.750697] Modules linked in: [ 1.753734] CPU: 0 UID: 0 PID: 41 Comm: kworker/u16:1 Not tainted 7.0.10-postmarketos-exynos4 #11 PREEMPT [ 1.763372] Hardware name: Samsung Exynos (Flattened Device Tree) [ 1.769446] Workqueue: events_unbound deferred_probe_work_func [ 1.775261] PC is at drm_mm_init+0x9c/0xa4 [ 1.779339] LR is at lima_vm_create+0x144/0x17c [ ... ] Fix the issue by moving the lima_vm_create() call after va_start and va_end are set up.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.2a1d2a6339961efc078208dc3b2f006e9e9a8e119
Vendor states this is fixed in 3b3bce4a692ac60d9f4a341e6b597dd1fd0a28f9 (fixed)
Vendor states this is fixed in 788917ba77f5d69bd368c1d176ecceda346a2951 (fixed)
Vendor states this is fixed in 79a3331ee436c8b1454f897d539606c9b5ebdf9f (fixed)
Vendor states this is fixed in ad4e908096dff97646f77b04e2e2825225e215f7 (fixed)
Vendor states this is fixed in af1f276d50c9d7ebcd25770f358ca503a89d96d7 (fixed)
Vendor states this is fixed in e0773ad25a34a49aece176721c466cf214e02222 (fixed)
Vendor states this is fixed in e2a7cee341986cb5b544a8286edc7fb0494c592e (fixed)
Vendor states this is fixed in fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.2 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card