| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025072557-CVE-2025-38362-8922@gregkh> Date: Fri, 25 Jul 2025 14:48:03 +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-38362: drm/amd/display: Add null pointer check for get_first_active_display() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Add null pointer check for get_first_active_display() The function mod_hdcp_hdcp1_enable_encryption() calls the function get_first_active_display(), but does not check its return value. The return value is a null pointer if the display list is empty. This will lead to a null pointer dereference in mod_hdcp_hdcp2_enable_encryption(). Add a null pointer check for get_first_active_display() and return MOD_HDCP_STATUS_DISPLAY_NOT_FOUND if the function return null. The Linux kernel CVE team has assigned CVE-2025-38362 to this issue. Affected and fixed versions =========================== Issue introduced in 5.8 with commit 2deade5ede56581722c0d7672f28b09548dc0fc4 and fixed in 5.15.187 with commit 34d3e10ab905f06445f8dbd8a3d9697095e71bae Issue introduced in 5.8 with commit 2deade5ede56581722c0d7672f28b09548dc0fc4 and fixed in 6.1.143 with commit 1ebcdf38887949def1a553ff3e45c98ed95a3cd0 Issue introduced in 5.8 with commit 2deade5ede56581722c0d7672f28b09548dc0fc4 and fixed in 6.6.96 with commit 5148c7ea69e9c5bf2f05081190f45ba96d3d1e7a Issue introduced in 5.8 with commit 2deade5ede56581722c0d7672f28b09548dc0fc4 and fixed in 6.12.36 with commit 4ce9f2dc9ff7cc410e8c5d936ec551e26b9599a9 Issue introduced in 5.8 with commit 2deade5ede56581722c0d7672f28b09548dc0fc4 and fixed in 6.15.5 with commit b3005145eab98d36777660b8893466e4f630ae1c Issue introduced in 5.8 with commit 2deade5ede56581722c0d7672f28b09548dc0fc4 and fixed in 6.16-rc1 with commit c3e9826a22027a21d998d3e64882fa377b613006 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-38362 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/modules/hdcp/hdcp_psp.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/34d3e10ab905f06445f8dbd8a3d9697095e71bae https://git.kernel.org/stable/c/1ebcdf38887949def1a553ff3e45c98ed95a3cd0 https://git.kernel.org/stable/c/5148c7ea69e9c5bf2f05081190f45ba96d3d1e7a https://git.kernel.org/stable/c/4ce9f2dc9ff7cc410e8c5d936ec551e26b9599a9 https://git.kernel.org/stable/c/b3005145eab98d36777660b8893466e4f630ae1c https://git.kernel.org/stable/c/c3e9826a22027a21d998d3e64882fa377b613006
Powered by blists - more mailing lists