data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2024-58012 in the interactive tracker

CVE-2024-58012

ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params

EPSS 0.2%

Published 2025-02-27 (20 months ago) by the Linux kernel CNA. Subsystem sound/soc. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2024-58012 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixiefixed6.12.15-1Update the kernel and reboot. Fixed in 6.12.15-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed6.12.15-1Update the kernel and reboot. Fixed in 6.12.15-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.12.15-1Update the kernel and reboot. Fixed in 6.12.15-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

sound/soc/sof/intel/hda-dai.c
sound/soc/sof/intel/hda.c

What this is
SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERSMAINTAINERS section matched on sound/soc/sof/ · sound-open-firmware@alsa-project.org · Supported
Kernel module
snd_sof_intel_hda_common

Check it on the machine

grep -wE 'CONFIG_SND|CONFIG_SND_SOC|CONFIG_SND_SOC_SOF_HDA_COMMON|CONFIG_SND_SOC_SOF_INTEL_TOPLEVEL' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w snd_sof_intel_hda_common

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

  • bookwormMnot built on amd64/cloud-amd64, arm64/arm64, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le
  • trixieMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
  • forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
M
a module where it is built at all; some flavours do not build it
Build switches
CONFIG_SND, CONFIG_SND_SOC, CONFIG_SND_SOC_SOF_HDA_COMMON, CONFIG_SND_SOC_SOF_INTEL_TOPLEVEL
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2025-02-27 (20 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.21%, higher than 11.0% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
sound/soc

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
5.76.12.14e012a77e4d76
5.76.13.3789a2fbf0900
5.76.14569922b82ca6

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2024-58012, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.