[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025100108-CVE-2025-39906-5913@gregkh>
Date: Wed, 1 Oct 2025 09:47:11 +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-39906: drm/amd/display: remove oem i2c adapter on finish
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: remove oem i2c adapter on finish
Fixes a bug where unbinding of the GPU would leave the oem i2c adapter
registered resulting in a null pointer dereference when applications try
to access the invalid device.
(cherry picked from commit 89923fb7ead4fdd37b78dd49962d9bb5892403e6)
The Linux kernel CVE team has assigned CVE-2025-39906 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 3d5470c973149f479572dcf4eea064775041ea6c and fixed in 6.16.8 with commit c686124bcf06253620790857ff462f00f3f7a4ab
Issue introduced in 6.15 with commit 3d5470c973149f479572dcf4eea064775041ea6c and fixed in 6.17 with commit 1dfd2864a1c4909147663e5a27c055f50f7c2796
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-39906
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/amd/display/amdgpu_dm/amdgpu_dm.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/c686124bcf06253620790857ff462f00f3f7a4ab
https://git.kernel.org/stable/c/1dfd2864a1c4909147663e5a27c055f50f7c2796
Powered by blists - more mailing lists