[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091615-CVE-2025-39820-50d7@gregkh>
Date: Tue, 16 Sep 2025 15:00:26 +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-39820: drm/msm/dpu: Add a null ptr check for dpu_encoder_needs_modeset
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/msm/dpu: Add a null ptr check for dpu_encoder_needs_modeset
The drm_atomic_get_new_connector_state() can return NULL if the
connector is not part of the atomic state. Add a check to prevent
a NULL pointer dereference.
This follows the same pattern used in dpu_encoder_update_topology()
within the same file, which checks for NULL before using conn_state.
Patchwork: https://patchwork.freedesktop.org/patch/665188/
The Linux kernel CVE team has assigned CVE-2025-39820 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 1ce69c265a53c61c5c29f97f542ff89af3f3d7e7 and fixed in 6.16.5 with commit aaec54254b02f5959c3670177037464d828b2140
Issue introduced in 6.15 with commit 1ce69c265a53c61c5c29f97f542ff89af3f3d7e7 and fixed in 6.17-rc4 with commit abebfed208515726760d79cf4f9f1a76b9a10a84
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-39820
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/msm/disp/dpu1/dpu_encoder.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/aaec54254b02f5959c3670177037464d828b2140
https://git.kernel.org/stable/c/abebfed208515726760d79cf4f9f1a76b9a10a84
Powered by blists - more mailing lists