CVE-2024-42088: ASoC: mediatek: mt8195: Add platform entry for ETDM1_OUT_BE dai link
In the Linux kernel, the following vulnerability has been resolved:
ASoC: mediatek: mt8195: Add platform entry for ETDM1_OUT_BE dai link
Commit e70b8dd26711 ("ASoC: mediatek: mt8195: Remove afe-dai component
and rework codec link") removed the codec entry for the ETDM1_OUT_BE
dai link entirely instead of replacing it with COMP_EMPTY(). This worked
by accident as the remaining COMP_EMPTY() platform entry became the codec
entry, and the platform entry became completely empty, effectively the
same as COMP_DUMMY() since snd_soc_fill_dummy_dai() doesn't do anything
for platform entries.
This causes a KASAN out-of-bounds warning in mtk_soundcard_common_probe()
in sound/soc/mediatek/common/mtk-soundcard-driver.c:
for_each_card_prelinks(card, i, dai_link) {
if (adsp_node && !strncmp(dai_link->name, "AFE_SOF", strlen("AFE_SOF")))
dai_link->platforms->of_node = adsp_node;
else if (!dai_link->platforms->name && !dai_link->platforms->of_node)
dai_link->platforms->of_node = platform_node;
}
where the code expects the platforms array to have space for at least one entry.
Add an COMP_EMPTY() entry so that dai_link->platforms has space.
Security readout for executives and security teams
Plain-English summary
A Linux audio-driver configuration error for MediaTek MT8195 can make the kernel access memory outside an allocated platform array during sound-card initialization. The reported impact includes limited data exposure, significant integrity compromise, and system disruption, but exploitation requires local low-privilege access.
Executive priority
Treat this as a targeted high-priority kernel update for MT8195-based devices, not an organization-wide internet emergency. Promptly identify applicable embedded or endpoint systems, confirm vendor-fixed builds, and schedule remediation according to device criticality and local-access exposure.
Technical view
The ETDM1_OUT_BE DAI link lost its codec entry without receiving the intended empty replacement. Its remaining platform entry was consequently interpreted as the codec, leaving no allocated platform slot. mtk_soundcard_common_probe() then dereferences dai_link->platforms as though an entry exists, producing a KASAN out-of-bounds warning. The referenced stable-kernel commits add COMP_EMPTY() to allocate that slot.
Likely exposure
Exposure appears limited to affected Linux kernels using the MediaTek MT8195 ASoC sound-card path. The supplied version data lists 6.8, 6.9.8, and 6.10 among affected identifiers, but does not clearly express complete version ranges. Confirm exact applicability against the running distribution's vendor advisory and backport history.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The bundle does not establish a practical exploit, public weaponization, remote reachability, or active exploitation. It is not listed in KEV.
Researcher notes
The source bundle provides no CWE and its affected-version representation is ambiguous, including an unexplained "0" identifier. The root cause and correction are specific and supported by upstream stable commits, but real-world exploitability and precise downstream distribution exposure are not established.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable referenced stable fix.
Confirm distribution backports because package versions may not directly match upstream kernel versions.
Prioritize MT8195 systems where the affected ASoC audio path is enabled or initialized.
Review vendor guidance before applying branch-specific kernel changes.
Validation and detection
Inventory kernel builds and identify systems using MediaTek MT8195 audio hardware.
Check vendor changelogs for the applicable referenced fix commit or documented backport.
Review kernel and KASAN logs for out-of-bounds warnings in mtk_soundcard_common_probe().
After updating, confirm sound-card initialization completes without related memory-safety warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-42088 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.