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 DF1461A3175 for ; Wed, 26 Feb 2025 01:58:01 +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=1740535081; cv=none; b=RsJaEtVkDk+VEKwOFh0623ALXjUiRbOopg7FxrD2Uur3yFEpjDbAnjcIRXk+WzkrHtlQK9jYEseHTJ4qlJw5EmWf8GhTQ3p+O2DWIX/g7D6KFgX0mt65oXOwhM8bsZuY4c2R5qIZh7EGpx3BvW0fJ/IO66dRix18V6H8c81cytg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740535081; c=relaxed/simple; bh=sFrlra+915B+ZQRAqzO5iNBdPttmz89k+blYQGzs33s=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=oaTVztD3EB78fP8gIGdri3PQTkTfAaj3I+1y1PaXTF9//TM5G3jLe59/trLgYH+cY5F/CP98eHruf3XEoMblK3xxIzLouTxoqKcJr8OCmQvaV9ea6LqhiBPaCLBF0UU9R7QFCBNFgAyI6okwHB1buG+s3Q6ks/io0D+bwRz17Jw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=MnWO/L+s; 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="MnWO/L+s" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 43C4FC4CEDD; Wed, 26 Feb 2025 01:58:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740535081; bh=sFrlra+915B+ZQRAqzO5iNBdPttmz89k+blYQGzs33s=; h=From:To:Cc:Subject:Date:Reply-to:From; b=MnWO/L+s77EWk99Sf8Ei5eooQcE8N/0ZRt/XCOgTTggMH/v28sqQ1PhPejH5y0RH7 Y41ZJMDKnCM1BI+Pu/kjYg042bBNoqF0DUEfUEic4C4Moss5mMSX9mElsny1s5Xi9e lOnyJi6VbRN758nw8G4YQv1/ZNrT6kYgxJGVwIf4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49083: iommu/omap: Fix regression in probe for NULL pointer dereference Date: Wed, 26 Feb 2025 02:54:48 +0100 Message-ID: <2025022657-CVE-2022-49083-34be@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=3231; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=sFrlra+915B+ZQRAqzO5iNBdPttmz89k+blYQGzs33s=; b=kA0DAAIRMUfUDdst+ykByyZiAGe+dDWjLkFk/AI1XXotmSuQtTjFdz55R4MVMceregPmaCXoJ YhdBAARAgAdFiEE9LYMxb94wiFKMT3LMUfUDdst+ykFAme+dDUACgkQMUfUDdst+ykOUwCgu7tW jPUokUPjp07O4mVHzN6gi8sAn3PR1S+7j/sEjJ3mLdvNElvVZvgj 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: iommu/omap: Fix regression in probe for NULL pointer dereference Commit 3f6634d997db ("iommu: Use right way to retrieve iommu_ops") started triggering a NULL pointer dereference for some omap variants: __iommu_probe_device from probe_iommu_group+0x2c/0x38 probe_iommu_group from bus_for_each_dev+0x74/0xbc bus_for_each_dev from bus_iommu_probe+0x34/0x2e8 bus_iommu_probe from bus_set_iommu+0x80/0xc8 bus_set_iommu from omap_iommu_init+0x88/0xcc omap_iommu_init from do_one_initcall+0x44/0x24 This is caused by omap iommu probe returning 0 instead of ERR_PTR(-ENODEV) as noted by Jason Gunthorpe . Looks like the regression already happened with an earlier commit 6785eb9105e3 ("iommu/omap: Convert to probe/release_device() call-backs") that changed the function return type and missed converting one place. The Linux kernel CVE team has assigned CVE-2022-49083 to this issue. Affected and fixed versions =========================== Issue introduced in 5.8 with commit 6785eb9105e3363aa51408c700a55e8b5f88fcf6 and fixed in 5.10.111 with commit bd905fed87ce01ac010011bb8f44ed0140116ceb Issue introduced in 5.8 with commit 6785eb9105e3363aa51408c700a55e8b5f88fcf6 and fixed in 5.15.34 with commit 47e239117bd97c8556f9187af7a9a7938db4e021 Issue introduced in 5.8 with commit 6785eb9105e3363aa51408c700a55e8b5f88fcf6 and fixed in 5.16.20 with commit ea518578aa8a9a0280605b53cc33f707e10c8178 Issue introduced in 5.8 with commit 6785eb9105e3363aa51408c700a55e8b5f88fcf6 and fixed in 5.17.3 with commit 1d89f2b9eadbcf3ce93c6d7238f68299a1f84968 Issue introduced in 5.8 with commit 6785eb9105e3363aa51408c700a55e8b5f88fcf6 and fixed in 5.18 with commit 71ff461c3f41f6465434b9e980c01782763e7ad8 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-49083 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/iommu/omap-iommu.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/bd905fed87ce01ac010011bb8f44ed0140116ceb https://git.kernel.org/stable/c/47e239117bd97c8556f9187af7a9a7938db4e021 https://git.kernel.org/stable/c/ea518578aa8a9a0280605b53cc33f707e10c8178 https://git.kernel.org/stable/c/1d89f2b9eadbcf3ce93c6d7238f68299a1f84968 https://git.kernel.org/stable/c/71ff461c3f41f6465434b9e980c01782763e7ad8