[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022656-CVE-2024-58012-90ce@gregkh>
Date: Wed, 26 Feb 2025 18:11:06 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-58012: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params
Each cpu DAI should associate with a widget. However, the topology might
not create the right number of DAI widgets for aggregated amps. And it
will cause NULL pointer deference.
Check that the DAI widget associated with the CPU DAI is valid to prevent
NULL pointer deference due to missing DAI widgets in topologies with
aggregated amps.
The Linux kernel CVE team has assigned CVE-2024-58012 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.14 with commit e012a77e4d7632cf615ba9625b1600ed8985c3b5
Fixed in 6.13.3 with commit 789a2fbf0900982788408d3b0034e0e3f914fb3b
Fixed in 6.14-rc1 with commit 569922b82ca660f8b24e705f6cf674e6b1f99cc7
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-2024-58012
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/soc/sof/intel/hda-dai.c
sound/soc/sof/intel/hda.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/e012a77e4d7632cf615ba9625b1600ed8985c3b5
https://git.kernel.org/stable/c/789a2fbf0900982788408d3b0034e0e3f914fb3b
https://git.kernel.org/stable/c/569922b82ca660f8b24e705f6cf674e6b1f99cc7
Powered by blists - more mailing lists