[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025070807-CVE-2025-38237-68e7@gregkh>
Date: Tue, 8 Jul 2025 09:43:07 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38237: media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode()
In fimc_is_hw_change_mode(), the function changes camera modes without
waiting for hardware completion, risking corrupted data or system hangs
if subsequent operations proceed before the hardware is ready.
Add fimc_is_hw_wait_intmsr0_intmsd0() after mode configuration, ensuring
hardware state synchronization and stable interrupt handling.
The Linux kernel CVE team has assigned CVE-2025-38237 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.295 with commit b0d92b94278561f43057003a73a17ce13b7c1a1a
Fixed in 5.10.239 with commit e4077a10a25560ec0bd0b42322e4ea027d6f76e2
Fixed in 5.15.186 with commit bb97dfab7615fea97322b8a6131546e80f878a69
Fixed in 6.15.4 with commit 14acbb5af101b7bb58c0952949bba4c5fdf0ee7e
Fixed in 6.16-rc1 with commit bd9f6ce7d512fa21249415c16af801a4ed5d97b6
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-2025-38237
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/samsung/exynos4-is/fimc-is-regs.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/b0d92b94278561f43057003a73a17ce13b7c1a1a
https://git.kernel.org/stable/c/e4077a10a25560ec0bd0b42322e4ea027d6f76e2
https://git.kernel.org/stable/c/bb97dfab7615fea97322b8a6131546e80f878a69
https://git.kernel.org/stable/c/14acbb5af101b7bb58c0952949bba4c5fdf0ee7e
https://git.kernel.org/stable/c/bd9f6ce7d512fa21249415c16af801a4ed5d97b6
Powered by blists - more mailing lists