Skip to main content
VulnerabilityPublished Updated

CVE-2026-93183: Linux kernel · drm/lima: call drm_mm_init() with a valid allocation range

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a, e0773ad25a34a49aece176721c466cf214e02222, e2a7cee341986cb5b544a8286edc7fb0494c592e +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119, < fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a
Fixed in
  • fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a
LinuxLinuxAffected
  • ≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119, < e0773ad25a34a49aece176721c466cf214e02222
Fixed in
  • e0773ad25a34a49aece176721c466cf214e02222
LinuxLinuxAffected
  • ≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119, < e2a7cee341986cb5b544a8286edc7fb0494c592e
Fixed in
  • e2a7cee341986cb5b544a8286edc7fb0494c592e
LinuxLinuxAffected
  • ≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119, < af1f276d50c9d7ebcd25770f358ca503a89d96d7
Fixed in
  • af1f276d50c9d7ebcd25770f358ca503a89d96d7
LinuxLinuxAffected
  • ≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119, < ad4e908096dff97646f77b04e2e2825225e215f7
Fixed in
  • ad4e908096dff97646f77b04e2e2825225e215f7
LinuxLinuxAffected
  • ≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119, < 788917ba77f5d69bd368c1d176ecceda346a2951
Fixed in
  • 788917ba77f5d69bd368c1d176ecceda346a2951

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.

References

Community reviews

Loading reviews…