| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2023-52850: media: hantro: Check whether reset op is defined before use |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| media: hantro: Check whether reset op is defined before use |
| |
| The i.MX8MM/N/P does not define the .reset op since reset of the VPU is |
| done by genpd. Check whether the .reset op is defined before calling it |
| to avoid NULL pointer dereference. |
| |
| Note that the Fixes tag is set to the commit which removed the reset op |
| from i.MX8M Hantro G2 implementation, this is because before this commit |
| all the implementations did define the .reset op. |
| |
| The Linux kernel CVE team has assigned CVE-2023-52850 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.18 with commit 6971efb70ac3e43d19bf33ef5f83bea0271831ee and fixed in 6.1.63 with commit 64f55cebb4339ae771e9e7f3f42bee2489e2fa00 |
| Issue introduced in 5.18 with commit 6971efb70ac3e43d19bf33ef5f83bea0271831ee and fixed in 6.5.12 with commit 66b4c5f980d741f3a47e4b65eeaf2797f2d59294 |
| Issue introduced in 5.18 with commit 6971efb70ac3e43d19bf33ef5f83bea0271831ee and fixed in 6.6.2 with commit 24c06295f28335ced3aad53dd4b0a0bae7b9b100 |
| Issue introduced in 5.18 with commit 6971efb70ac3e43d19bf33ef5f83bea0271831ee and fixed in 6.7 with commit 88d4b23a629ebd34f682f770cb6c2116c851f7b8 |
| |
| 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-2023-52850 |
| 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/media/platform/verisilicon/hantro_drv.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/64f55cebb4339ae771e9e7f3f42bee2489e2fa00 |
| https://git.kernel.org/stable/c/66b4c5f980d741f3a47e4b65eeaf2797f2d59294 |
| https://git.kernel.org/stable/c/24c06295f28335ced3aad53dd4b0a0bae7b9b100 |
| https://git.kernel.org/stable/c/88d4b23a629ebd34f682f770cb6c2116c851f7b8 |
