Kernel crash via premature allocation-range initialization
Published Sep 17, 2026 · Updated Sep 17, 2026
Initialization-order error in Linux's Lima GPU driver allows local users to cause a kernel crash during driver probing. lima_vm_create() passes zero-valued va_start and va_end to drm_mm_init() before those bounds are initialized. The observed kernel BUG requires DRM_DEBUG_MM and Lima driver initialization; the upstream report does not establish an attacker-controlled trigger.
Summary
What happened
Initialization-order error in Linux's Lima GPU driver allows local users to cause a kernel crash during driver probing. lima_vm_create() passes zero-valued va_start and va_end to drm_mm_init() before those bounds are initialized. The observed kernel BUG requires DRM_DEBUG_MM and Lima driver initialization; the upstream report does not establish an attacker-controlled trigger.
The record
- CVE
- CVE-2026-93183
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <3b3bce4a692ac60d9f4a341e6b597dd1fd0a28f9
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <788917ba77f5d69bd368c1d176ecceda346a2951
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <79a3331ee436c8b1454f897d539606c9b5ebdf9f
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <ad4e908096dff97646f77b04e2e2825225e215f7
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <af1f276d50c9d7ebcd25770f358ca503a89d96d7
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <e0773ad25a34a49aece176721c466cf214e02222
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <e2a7cee341986cb5b544a8286edc7fb0494c592e
- Affected versionversion=a1d2a6339961efc078208dc3b2f006e9e9a8e119 <fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started