Message-ID: <2025072509-CVE-2025-38467-eb0c@gregkh>
Date: Fri, 25 Jul 2025 17:28:29 +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-38467: drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

drm/exynos: exynos7_drm_decon: add vblank check in IRQ handling

If there's support for another console device (such as a TTY serial),
the kernel occasionally panics during boot. The panic message and a
relevant snippet of the call stack is as follows:

  Unable to handle kernel NULL pointer dereference at virtual address 000000000000000
  Call trace:
    drm_crtc_handle_vblank+0x10/0x30 (P)
    decon_irq_handler+0x88/0xb4
    [...]

Otherwise, the panics don't happen. This indicates that it's some sort
of race condition.

Add a check to validate if the drm device can handle vblanks before
calling drm_crtc_handle_vblank() to avoid this.

The Linux kernel CVE team has assigned CVE-2025-38467 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.0 with commit 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 and fixed in 5.4.296 with commit b4e72c0bf878f02faa00a7dc7c9ffc4ff7c116a7
	Issue introduced in 4.0 with commit 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 and fixed in 5.10.240 with commit a2130463fc9451005660b0eda7b61d5f746f7d74
	Issue introduced in 4.0 with commit 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 and fixed in 5.15.189 with commit 87825fbd1e176cd5b896940f3959e7c9a916945d
	Issue introduced in 4.0 with commit 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 and fixed in 6.1.146 with commit a40a35166f7e4f6dcd4b087d620c8228922dcb0a
	Issue introduced in 4.0 with commit 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 and fixed in 6.6.99 with commit 391e5ea5b877230b844c9bd8bbcd91b681b1ce2d
	Issue introduced in 4.0 with commit 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 and fixed in 6.12.39 with commit e9d9b25f376737b81f06de9c5aa422b488f47184
	Issue introduced in 4.0 with commit 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 and fixed in 6.15.7 with commit 996740652e620ef8ee1e5c65832cf2ffa498577d
	Issue introduced in 4.0 with commit 96976c3d9aff4e1387c30f6356ac01fa6f72ef46 and fixed in 6.16-rc5 with commit b846350aa272de99bf6fecfa6b08e64ebfb13173

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-38467
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/exynos/exynos7_drm_decon.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/b4e72c0bf878f02faa00a7dc7c9ffc4ff7c116a7
	https://git.kernel.org/stable/c/a2130463fc9451005660b0eda7b61d5f746f7d74
	https://git.kernel.org/stable/c/87825fbd1e176cd5b896940f3959e7c9a916945d
	https://git.kernel.org/stable/c/a40a35166f7e4f6dcd4b087d620c8228922dcb0a
	https://git.kernel.org/stable/c/391e5ea5b877230b844c9bd8bbcd91b681b1ce2d
	https://git.kernel.org/stable/c/e9d9b25f376737b81f06de9c5aa422b488f47184
	https://git.kernel.org/stable/c/996740652e620ef8ee1e5c65832cf2ffa498577d
	https://git.kernel.org/stable/c/b846350aa272de99bf6fecfa6b08e64ebfb13173

Powered by blists - more mailing lists