LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38299: ASoC: mediatek: mt8195: Set ETDM1/2 IN/OUT to COMP_DUMMY()

In the Linux kernel, the following vulnerability has been resolved: ASoC: mediatek: mt8195: Set ETDM1/2 IN/OUT to COMP_DUMMY() ETDM2_IN_BE and ETDM1_OUT_BE are defined as COMP_EMPTY(), in the case the codec dai_name will be null. Avoid a crash if the device tree is not assigning a codec to these links. [ 1.179936] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 1.181065] Mem abort info: [ 1.181420] ESR = 0x0000000096000004 [ 1.181892] EC = 0x25: DABT (current EL), IL = 32 bits [ 1.182576] SET = 0, FnV = 0 [ 1.182964] EA = 0, S1PTW = 0 [ 1.183367] FSC = 0x04: level 0 translation fault [ 1.183983] Data abort info: [ 1.184406] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 [ 1.185097] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 1.185766] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 1.186439] [0000000000000000] user address but active_mm is swapper [ 1.187239] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP [ 1.188029] Modules linked in: [ 1.188420] CPU: 7 UID: 0 PID: 70 Comm: kworker/u32:1 Not tainted 6.14.0-rc4-next-20250226+ #85 [ 1.189515] Hardware name: Radxa NIO 12L (DT) [ 1.190065] Workqueue: events_unbound deferred_probe_work_func [ 1.190808] pstate: 40400009 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1.191683] pc : __pi_strcmp+0x24/0x140 [ 1.192170] lr : mt8195_mt6359_soc_card_probe+0x224/0x7b0 [ 1.192854] sp : ffff800083473970 [ 1.193271] x29: ffff800083473a10 x28: 0000000000001008 x27: 0000000000000002 [ 1.194168] x26: ffff800082408960 x25: ffff800082417db0 x24: ffff800082417d88 [ 1.195065] x23: 000000000000001e x22: ffff800082dbf480 x21: ffff800082dc07b8 [ 1.195961] x20: 0000000000000000 x19: 0000000000000013 x18: 00000000ffffffff [ 1.196858] x17: 000000040044ffff x16: 005000f2b5503510 x15: 0000000000000006 [ 1.197755] x14: ffff800082407af0 x13: 6e6f69737265766e x12: 692d6b636f6c6374 [ 1.198651] x11: 0000000000000002 x10: ffff80008240b920 x9 : 0000000000000018 [ 1.199547] x8 : 0101010101010101 x7 : 0000000000000000 x6 : 0000000000000000 [ 1.200443] x5 : 0000000000000000 x4 : 8080808080000000 x3 : 303933383978616d [ 1.201339] x2 : 0000000000000000 x1 : ffff80008240b920 x0 : 0000000000000000 [ 1.202236] Call trace: [ 1.202545] __pi_strcmp+0x24/0x140 (P) [ 1.203029] mtk_soundcard_common_probe+0x3bc/0x5b8 [ 1.203644] platform_probe+0x70/0xe8 [ 1.204106] really_probe+0xc8/0x3a0 [ 1.204556] __driver_probe_device+0x84/0x160 [ 1.205104] driver_probe_device+0x44/0x130 [ 1.205630] __device_attach_driver+0xc4/0x170 [ 1.206189] bus_for_each_drv+0x8c/0xf8 [ 1.206672] __device_attach+0xa8/0x1c8 [ 1.207155] device_initial_probe+0x1c/0x30 [ 1.207681] bus_probe_device+0xb0/0xc0 [ 1.208165] deferred_probe_work_func+0xa4/0x100 [ 1.208747] process_one_work+0x158/0x3e0 [ 1.209254] worker_thread+0x2c4/0x3e8 [ 1.209727] kthread+0x134/0x1f0 [ 1.210136] ret_from_fork+0x10/0x20 [ 1.210589] Code: 54000401 b50002c6 d503201f f86a6803 (f8408402) [ 1.211355] ---[ end trace 0000000000000000 ]---

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

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.
  • Prioritize affected embedded devices where kernel probe failures impair essential operations.

Validation and detection

  • Inventory devices using the MediaTek MT8195 ASoC driver and record exact kernel builds.
  • Compare kernel source or vendor changelogs against the four cited stable commits.
  • Inspect device-tree audio links for missing codec assignments on ETDM1_OUT_BE and ETDM2_IN_BE.
  • Review boot logs for NULL dereferences involving mt8195 sound-card probing or __pi_strcmp.
Prepared
Confidence
medium
Sources
6

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.

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
0ADP providers
5Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux81051a495a9a23c0339d2ae1aa6e4477ed7268c8, e70b8dd26711704b1ff1f1b4eb3d048ba69e29da, e70b8dd26711704b1ff1f1b4eb3d048ba69e29da, e70b8dd26711704b1ff1f1b4eb3d048ba69e29daunaffected
LinuxLinux6.8, 0, 6.12.34, 6.15.3, 6.16affected
Weakness

CWE details

No CWE listed

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