CVE-2026-93183 — drm/lima: call drm_mm_init() with a valid allocation range
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119 and < af1f276d50c9d7ebcd25770f358ca503a89d96d7≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119 and < fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119 and < ad4e908096dff97646f77b04e2e2825225e215f7≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119 and < 788917ba77f5d69bd368c1d176ecceda346a2951≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119 and < 79a3331ee436c8b1454f897d539606c9b5ebdf9f≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119 and < e2a7cee341986cb5b544a8286edc7fb0494c592e≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119 and < e0773ad25a34a49aece176721c466cf214e02222≥ a1d2a6339961efc078208dc3b2f006e9e9a8e119 and < 3b3bce4a692ac60d9f4a341e6b597dd1fd0a28f9 and 1 moreversion 5.2 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/3b3bce4a692ac60d9f4a341e6b597dd1fd0a28f9
- git.kernel.org/stable/c/ad4e908096dff97646f77b04e2e2825225e215f7
- git.kernel.org/stable/c/e2a7cee341986cb5b544a8286edc7fb0494c592e
- git.kernel.org/stable/c/af1f276d50c9d7ebcd25770f358ca503a89d96d7
- git.kernel.org/stable/c/79a3331ee436c8b1454f897d539606c9b5ebdf9f
- git.kernel.org/stable/c/fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a
- git.kernel.org/stable/c/e0773ad25a34a49aece176721c466cf214e02222
- git.kernel.org/stable/c/788917ba77f5d69bd368c1d176ecceda346a2951
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 16h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 16h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93183 is "drm/lima: call drm_mm_init() with a valid allocation range", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.