LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35842: ASoC: mediatek: sof-common: Add NULL check for normal_link string

In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: sof-common: Add NULL check for normal_link string It's not granted that all entries of struct sof_conn_stream declare a `normal_link` (a non-SOF, direct link) string, and this is the case for SoCs that support only SOF paths (hence do not support both direct and SOF usecases). For example, in the case of MT8188 there is no normal_link string in any of the sof_conn_stream entries and there will be more drivers doing that in the future. To avoid possible NULL pointer KPs, add a NULL check for `normal_link`.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a kernel panic when MediaTek SOF audio code assumes a link name exists when it may be absent. The public record does not show active exploitation, CVSS scoring, or a defined attack path. Business urgency depends on whether affected MediaTek-based Linux devices are in use.

Executive priority

Handle through normal kernel patch management unless the organization operates MediaTek-based Linux fleets where unexpected reboots would disrupt operations. Evidence is insufficient to justify emergency response without local exposure details or vendor-specific severity.

Technical view

CVE-2024-35842 fixes a NULL pointer kernel panic risk in Linux ASoC MediaTek sof-common handling of sof_conn_stream normal_link. Some SoCs, including MT8188, support only SOF paths and omit normal_link. The fix adds a NULL check before using that string.

Likely exposure

Exposure appears limited to Linux kernels in the affected version ranges running relevant MediaTek ASoC SOF audio driver paths. The bundle lists Linux 6.0 and affected stable branches including 6.1.75, 6.6.14, 6.7.2, and 6.8, but product-specific distro backport status is not provided.

Exploitation context

The sources describe a possible NULL pointer kernel panic, not code execution. There is no KEV listing and no cited evidence of active exploitation. The bundle does not define whether triggering requires local access, specific hardware, audio initialization, or a particular user action.

Researcher notes

The key uncertainty is triggerability. The record identifies a defensive NULL check for absent normal_link entries, but does not document reachable call paths, privilege requirements, or affected device models beyond MediaTek SoC context and the MT8188 example.

Mitigation direction

  • Apply vendor or distribution kernel updates that include the referenced stable fixes.
  • Prioritize MediaTek-based Linux systems using SOF audio paths.
  • Check vendor advisories for exact fixed package versions and backport status.
  • Monitor CVE and kernel stable updates for any revised severity or exploit information.

Validation and detection

  • Inventory Linux kernel versions and MediaTek SoC hardware in managed assets.
  • Confirm whether affected systems load MediaTek ASoC SOF-related drivers.
  • Verify deployed kernels include one of the referenced stable fix commits or vendor backports.
  • Review system logs for NULL pointer kernel panics involving MediaTek SOF audio paths.
Prepared
Confidence
medium
Sources
6

Public sources used

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-35842 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0caf1120c58395108344d5df4e09359b67e95094, 0caf1120c58395108344d5df4e09359b67e95094, 0caf1120c58395108344d5df4e09359b67e95094, 0caf1120c58395108344d5df4e09359b67e95094unaffected
LinuxLinux6.0, 0, 6.1.75, 6.6.14, 6.7.2, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.