From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AD070541E52 for ; Thu, 17 Sep 2026 16:41:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789663269; cv=none; b=Mmjm7uYPugUxghnNrOG7/RlFvgrK1iJbJMwawVTROfjaJOscO+Ixynu0Gl7yY7DVo5xosU6bMhP/G84ppdMdw207oBlxCMkaBv6PpF9ou6Xgyuwa3WGBWw9uvIcnPpW+6n4e47raGSr5kgZWhUMh+Zqc6+G2IGA2qCEEf37VCoc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789663269; c=relaxed/simple; bh=kDqPRa8jGZaJr1XoikYdwGEazh/ZfOPcIpCE4KdoG5U=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=uWTb5VN6X8O7gPAGzzrJMbwpZCZDx70pN3Ym4+DEyMOFZfpN6fuSJBcZ4WaOu/hvAQx8HQHkN7MDpP7BC7yrbUxaPhqf9FI4ULpzfoQHhnN0lEEPFeRQSyuyGSet8vnVC95A+Vq4b/n7keIssD7PeFLAM8x2KmEbC8q9sWcZNzs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Ax77jUeT; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="Ax77jUeT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 119011F000FF; Thu, 17 Sep 2026 16:41:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789663267; bh=kuGyMLvqxDk6h25g53D3efwIHit8w8Gax4V4Y5ZJSXg=; h=From:To:Cc:Subject:Date:Reply-To; b=Ax77jUeT82ay9oxrHOkwejyw8WHKFKZob52sxskFD4uNMAOoU2i7RMa7u4zDIFjmB jHgipkj0LTcTvOPAaCRvMJY1ZmobWB3FEWzfFj98bXrD/JFxhlJAiv9CkfJMEf5+QR 20jKUl1CU/ddD8xXokWsEZgr4D0amf6GIS8P8cjM= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-93183: drm/lima: call drm_mm_init() with a valid allocation range Date: Thu, 17 Sep 2026 17:17:40 +0100 Message-ID: <2026091702-CVE-2026-93183-fb42@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4102; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=GuRBUf9CeQnrIJzNRXZ2dodJdF2ne2dx1NX+gIvBGZ4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBG7VLV+tfXpXbeYGB0GT4sPPGDzXuB7V0dkV8OB6x m0Xi5T9HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRdykMc6W/3HmworPgUfQM kbqVqfVSQietJjLMT+KRYeAQXehce2f6iYKfM0v0D7l8AQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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. The Linux kernel CVE team has assigned CVE-2026-93183 to this issue. Affected and fixed versions =========================== Issue introduced in 5.2 with commit a1d2a6339961efc078208dc3b2f006e9e9a8e119 and fixed in 5.10.270 with commit af1f276d50c9d7ebcd25770f358ca503a89d96d7 Issue introduced in 5.2 with commit a1d2a6339961efc078208dc3b2f006e9e9a8e119 and fixed in 5.15.221 with commit fd6bc5f1d6b54047b06b82bab25a7e21e4b1c95a Issue introduced in 5.2 with commit a1d2a6339961efc078208dc3b2f006e9e9a8e119 and fixed in 6.1.188 with commit ad4e908096dff97646f77b04e2e2825225e215f7 Issue introduced in 5.2 with commit a1d2a6339961efc078208dc3b2f006e9e9a8e119 and fixed in 6.6.157 with commit 788917ba77f5d69bd368c1d176ecceda346a2951 Issue introduced in 5.2 with commit a1d2a6339961efc078208dc3b2f006e9e9a8e119 and fixed in 6.12.110 with commit 79a3331ee436c8b1454f897d539606c9b5ebdf9f Issue introduced in 5.2 with commit a1d2a6339961efc078208dc3b2f006e9e9a8e119 and fixed in 6.18.52 with commit e2a7cee341986cb5b544a8286edc7fb0494c592e Issue introduced in 5.2 with commit a1d2a6339961efc078208dc3b2f006e9e9a8e119 and fixed in 7.2.6 with commit e0773ad25a34a49aece176721c466cf214e02222 Issue introduced in 5.2 with commit a1d2a6339961efc078208dc3b2f006e9e9a8e119 and fixed in 7.3-rc1 with commit 3b3bce4a692ac60d9f4a341e6b597dd1fd0a28f9 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-93183 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/gpu/drm/lima/lima_device.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: 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