[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025070330-CVE-2025-38130-3371@gregkh>
Date: Thu, 3 Jul 2025 10:35:47 +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-38130: drm/connector: only call HDMI audio helper plugged cb if non-null
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/connector: only call HDMI audio helper plugged cb if non-null
On driver remove, sound/soc/codecs/hdmi-codec.c calls the plugged_cb
with NULL as the callback function and codec_dev, as seen in its
hdmi_remove function.
The HDMI audio helper then happily tries calling said null function
pointer, and produces an Oops as a result.
Fix this by only executing the callback if fn is non-null. This means
the .plugged_cb and .plugged_cb_dev members still get appropriately
cleared.
The Linux kernel CVE team has assigned CVE-2025-38130 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit baf616647fe6f857a0cf2187197de31e9bb17a71 and fixed in 6.15.3 with commit 933f3eab1d489af8d734bff855b10d29dd5968a4
Issue introduced in 6.14 with commit baf616647fe6f857a0cf2187197de31e9bb17a71 and fixed in 6.16-rc1 with commit be9b3f9a54101c19226c25ba7163d291183777a0
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-38130
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/display/drm_hdmi_audio_helper.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/933f3eab1d489af8d734bff855b10d29dd5968a4
https://git.kernel.org/stable/c/be9b3f9a54101c19226c25ba7163d291183777a0
Powered by blists - more mailing lists