[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024122735-CVE-2024-53225-8deb@gregkh>
Date: Fri, 27 Dec 2024 14:53:11 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-53225: iommu/tegra241-cmdqv: Fix alignment failure at max_n_shift
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iommu/tegra241-cmdqv: Fix alignment failure at max_n_shift
When configuring a kernel with PAGE_SIZE=4KB, depending on its setting of
CONFIG_CMA_ALIGNMENT, VCMDQ_LOG2SIZE_MAX=19 could fail the alignment test
and trigger a WARN_ON:
WARNING: at drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:3646
Call trace:
arm_smmu_init_one_queue+0x15c/0x210
tegra241_cmdqv_init_structures+0x114/0x338
arm_smmu_device_probe+0xb48/0x1d90
Fix it by capping max_n_shift to CMDQ_MAX_SZ_SHIFT as SMMUv3 CMDQ does.
The Linux kernel CVE team has assigned CVE-2024-53225 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 and fixed in 6.12.2 with commit 85a1d70b86dbcb84a68e7e4942a5181276945988
Issue introduced in 6.12 with commit 918eb5c856f6ce4cf93b4b38e4b5e156905c5943 and fixed in 6.13-rc1 with commit a3799717b881aa0f4e722afb70e7b8ba84ae4f36
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-2024-53225
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/arm/arm-smmu-v3/tegra241-cmdqv.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/85a1d70b86dbcb84a68e7e4942a5181276945988
https://git.kernel.org/stable/c/a3799717b881aa0f4e722afb70e7b8ba84ae4f36
Powered by blists - more mailing lists