{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93183 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93183 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93183 and fix it if it is affected.\n\nWhat it is: CVE-2026-93183 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93183 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93183/ (Markdown: https://insights.sbomify.com/CVE-2026-93183/index.md)","id":"CVE-2026-93183","markdown":"https://insights.sbomify.com/CVE-2026-93183/index.md","name":"CVE-2026-93183","record":{"aliases":["AZL-102719","DEBIAN-CVE-2026-93183","GHSA-9h28-6jf6-ffg7","UBUNTU-CVE-2026-93183"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A kernel bug in the Lima DRM driver causes a crash when debug memory management is enabled, leading to local denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/lima: call drm_mm_init() with a valid allocation range\n\nlima_vm_create() is currently run before va_start and va_end are set up,\nmeaning they are both 0. lima_vm_create() runs drm_mm_init() with them\nas arguments for the allocator, and if DRM_DEBUG_MM is enabled the\nDRM_MM_BUG_ON check in drm_mm_init then fires, as seen here on\nexynos4412-odroid-u2:\n\n[    1.736297] ------------[ cut here ]------------\n[    1.740370] kernel BUG at drivers/gpu/drm/drm_mm.c:931!\n[    1.745574] Internal error: Oops - BUG: 0 [#1] SMP ARM\n[    1.750697] Modules linked in:\n[    1.753734] CPU: 0 UID: 0 PID: 41 Comm: kworker/u16:1 Not tainted 7.0.10-postmarketos-exynos4 #11 PREEMPT\n[    1.763372] Hardware name: Samsung Exynos (Flattened Device Tree)\n[    1.769446] Workqueue: events_unbound deferred_probe_work_func\n[    1.775261] PC is at drm_mm_init+0x9c/0xa4\n[    1.779339] LR is at lima_vm_create+0x144/0x17c\n[ ... ]\n\nFix the issue by moving the lima_vm_create() call after va_start and\nva_end are set up.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/lima: call drm_mm_init() with a valid allocation range","id":"CVE-2026-93183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ASoC: fsl_audmix: rework runtime PM handling in probe","id":"CVE-2026-93184"},"packages":[],"prev":{"headline":"sched/fair: Fix overflow in update_tg_cfs_runnable()","id":"CVE-2026-93182"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A kernel bug in the Lima DRM driver causes a crash when debug memory management is enabled, leading to local denial of service.","url":"https://insights.sbomify.com/CVE-2026-93183/"}