[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121632-CVE-2025-68205-6672@gregkh>
Date: Tue, 16 Dec 2025 14:54:34 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68205: ALSA: hda/hdmi: Fix breakage at probing nvhdmi-mcp driver
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ALSA: hda/hdmi: Fix breakage at probing nvhdmi-mcp driver
After restructuring and splitting the HDMI codec driver code, each
HDMI codec driver contains the own build_controls and build_pcms ops.
A copy-n-paste error put the wrong entries for nvhdmi-mcp driver; both
build_controls and build_pcms are swapped. Unfortunately both
callbacks have the very same form, and the compiler didn't complain
it, either. This resulted in a NULL dereference because the PCM
instance hasn't been initialized at calling the build_controls
callback.
Fix it by passing the proper entries.
The Linux kernel CVE team has assigned CVE-2025-68205 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.17 with commit ad781b550f9a8829e3dae4bd3d18c4a126a53d04 and fixed in 6.17.9 with commit d2aed6fac1148528181affb781aa683d6569042b
Issue introduced in 6.17 with commit ad781b550f9a8829e3dae4bd3d18c4a126a53d04 and fixed in 6.18 with commit 82420bd4e17bdaba8453fbf9e10c58c9ed0c9727
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-68205
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:
sound/hda/codecs/hdmi/nvhdmi-mcp.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/d2aed6fac1148528181affb781aa683d6569042b
https://git.kernel.org/stable/c/82420bd4e17bdaba8453fbf9e10c58c9ed0c9727
Powered by blists - more mailing lists