From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 EA1E621772C for ; Wed, 26 Feb 2025 02:14:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536092; cv=none; b=dLdsTbOGlsvqjfbVIJuKZIkXzGZmbBqT8Z6sbf//y7Ui7VJDlLzD+0FchbwPgEcUggBFh8rmTN77XzR9TIMw5JaURt3pFN08DxOS+qAs7qx7KwlbAaSUe+LXcu3MajM6nYTJeFtgf9dJa/mEOoZjMXGRSofWdEjwg8duIIJ0jpI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536092; c=relaxed/simple; bh=MZzyGpHEBHJtlpDArzqYW2EzGg+TOimIjQF+g8v1O6E=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=jDpkglMwfNWnkFoRBKfR7V5LZJ9EbkCnzVJuDRkqidZBVvKVmx+x9VXmBAfVUMEQKIsEfwQ6mEOoaKD8INGJ22YNHNT1ECnFFqB4eYgHTcMmBOEpBa1ZieEzsbEe/SSLq0Kxr+yju7iQw3MbT/ZyYrrtERQTgMaV1C4QpJCpUXE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=NecLKGt/; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="NecLKGt/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BFC6AC4CEDD; Wed, 26 Feb 2025 02:14:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740536091; bh=MZzyGpHEBHJtlpDArzqYW2EzGg+TOimIjQF+g8v1O6E=; h=From:To:Cc:Subject:Date:Reply-to:From; b=NecLKGt/3jr59NU3IPVo9DgVdPCyYSWXVJkDI/sU/h0JJBnArHd6Rp/0pW17lsVZZ zazFiRtOjZI2+OGgvGE8Ey/vB4oC1Iz0YPyxWPDc5IaX6YY0ESZvCtmaGqF8sNUL5+ gwcK8dMxOjGSDaA+TPd6Z1rA5Xu4oQ736bxZ2K5o= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49483: drm/msm/disp/dpu1: avoid clearing hw interrupts if hw_intr is null during drm uninit Date: Wed, 26 Feb 2025 03:12:37 +0100 Message-ID: <2025022604-CVE-2022-49483-dd7b@gregkh> X-Mailer: git-send-email 2.48.1 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=2930; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=MZzyGpHEBHJtlpDArzqYW2EzGg+TOimIjQF+g8v1O6E=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7yv/YfdhzJn3pUdsuSYHn5u/XhG3SaUgt6cxr31V39 n2O/o+IjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjI7icM82P8Jm9amtzk9El+ 4Tx9qcvX4ng+PGZYcDNcxmqu149Lbp3ObqvEmPTLBbWFAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/msm/disp/dpu1: avoid clearing hw interrupts if hw_intr is null during drm uninit If edp modeset init is failed due to panel being not ready and probe defers during drm bind, avoid clearing irqs and dereference hw_intr when hw_intr is null. BUG: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 Call trace: dpu_core_irq_uninstall+0x50/0xb0 dpu_irq_uninstall+0x18/0x24 msm_drm_uninit+0xd8/0x16c msm_drm_bind+0x580/0x5fc try_to_bring_up_master+0x168/0x1c0 __component_add+0xb4/0x178 component_add+0x1c/0x28 dp_display_probe+0x38c/0x400 platform_probe+0xb0/0xd0 really_probe+0xcc/0x2c8 __driver_probe_device+0xbc/0xe8 driver_probe_device+0x48/0xf0 __device_attach_driver+0xa0/0xc8 bus_for_each_drv+0x8c/0xd8 __device_attach+0xc4/0x150 device_initial_probe+0x1c/0x28 Changes in V2: - Update commit message and coreect fixes tag. Patchwork: https://patchwork.freedesktop.org/patch/484430/ The Linux kernel CVE team has assigned CVE-2022-49483 to this issue. Affected and fixed versions =========================== Issue introduced in 5.16 with commit f25f656608e3a54ac3e0747be415cf3d4a69cef8 and fixed in 5.17.14 with commit a7ca30c3a8b2e8bda65f2b922d382ac056be8aa4 Issue introduced in 5.16 with commit f25f656608e3a54ac3e0747be415cf3d4a69cef8 and fixed in 5.18.3 with commit a800701429313149afde18d98821554fbfcb3164 Issue introduced in 5.16 with commit f25f656608e3a54ac3e0747be415cf3d4a69cef8 and fixed in 5.19 with commit 01013ba9bbddc62f7d011163cebfd7ed06bb698b 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-2022-49483 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/msm/disp/dpu1/dpu_hw_interrupts.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/a7ca30c3a8b2e8bda65f2b922d382ac056be8aa4 https://git.kernel.org/stable/c/a800701429313149afde18d98821554fbfcb3164 https://git.kernel.org/stable/c/01013ba9bbddc62f7d011163cebfd7ed06bb698b