Security readout for executives and security teams
Plain-English summary
A Linux audio driver flaw can trigger a kernel null-pointer error while initializing certain MediaTek MT8195 devices. It occurs when the device tree does not assign a codec to specific audio links. The documented consequence is a kernel oops during device probing, potentially disrupting audio initialization or device availability.
Executive priority
Routine for most environments, but elevated for operationally important MT8195-based appliances with custom device trees. Confirm exposure during the next kernel maintenance cycle. Expedite remediation if boot logs show probe crashes or if affected audio initialization supports safety-critical or customer-facing functions.
Technical view
ETDM2_IN_BE and ETDM1_OUT_BE used empty component definitions, allowing a null codec DAI name. The MT8195 sound-card probe subsequently passed that null value into string comparison, causing a kernel NULL-pointer dereference during deferred probing. The stable changes replace the empty definitions with dummy components.
Likely exposure
Exposure appears limited to Linux systems using the MediaTek MT8195 ASoC sound configuration where affected ETDM links lack codec assignments in the device tree. The supplied version data includes Linux 6.8, 6.12.34, 6.15.3, and 6.16, but its range semantics are unclear; verify exposure by kernel commit and vendor build.
Exploitation context
The bundle documents a configuration-dependent crash but provides no evidence of active exploitation, remote reachability, privilege escalation, or code execution. CVE-2025-38299 is not listed as KEV in the supplied data. Treat the known impact as availability and initialization failure unless vendor analysis establishes broader consequences.
Researcher notes
The supplied trace shows a null argument reaching __pi_strcmp from mtk_soundcard_common_probe during deferred probe work on a Radxa NIO 12L. Evidence supports a deterministic configuration-triggered NULL dereference. No CVSS, CWE, attack prerequisites, or demonstrated security boundary crossing are supplied, and the affected-version metadata requires commit-level interpretation.
Mitigation direction
Update to a vendor kernel containing the applicable cited stable fix.
Check vendor advisories for corrected package versions matching each deployed kernel branch.
Review MT8195 device trees for unassigned codecs on the affected ETDM links.
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-2025-38299 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jul 10, 2025, 07:42 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.