LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38486: soundwire: Revert "soundwire: qcom: Add set_channel_map api support"

In the Linux kernel, the following vulnerability has been resolved: soundwire: Revert "soundwire: qcom: Add set_channel_map api support" This reverts commit 7796c97df6b1b2206681a07f3c80f6023a6593d5. This patch broke Dragonboard 845c (sdm845). I see: Unexpected kernel BRK exception at EL1 Internal error: BRK handler: 00000000f20003e8 [#1] SMP pc : qcom_swrm_set_channel_map+0x7c/0x80 [soundwire_qcom] lr : snd_soc_dai_set_channel_map+0x34/0x78 Call trace: qcom_swrm_set_channel_map+0x7c/0x80 [soundwire_qcom] (P) sdm845_dai_init+0x18c/0x2e0 [snd_soc_sdm845] snd_soc_link_init+0x28/0x6c snd_soc_bind_card+0x5f4/0xb0c snd_soc_register_card+0x148/0x1a4 devm_snd_soc_register_card+0x50/0xb0 sdm845_snd_platform_probe+0x124/0x148 [snd_soc_sdm845] platform_probe+0x6c/0xd0 really_probe+0xc0/0x2a4 __driver_probe_device+0x7c/0x130 driver_probe_device+0x40/0x118 __device_attach_driver+0xc4/0x108 bus_for_each_drv+0x8c/0xf0 __device_attach+0xa4/0x198 device_initial_probe+0x18/0x28 bus_probe_device+0xb8/0xbc deferred_probe_work_func+0xac/0xfc process_one_work+0x244/0x658 worker_thread+0x1b4/0x360 kthread+0x148/0x228 ret_from_fork+0x10/0x20 Kernel panic - not syncing: BRK handler: Fatal exception Dan has also reported following issues with the original patch https://lore.kernel.org/all/33fe8fe7-719a-405a-9ed2-d9f816ce1d57@sabinyo.mountain/ Bug #1: The zeroeth element of ctrl->pconfig[] is supposed to be unused. We start counting at 1. However this code sets ctrl->pconfig[0].ch_mask = 128. Bug #2: There are SLIM_MAX_TX_PORTS (16) elements in tx_ch[] array but only QCOM_SDW_MAX_PORTS + 1 (15) in the ctrl->pconfig[] array so it corrupts memory like Yongqin Liu pointed out. Bug 3: Like Jie Gan pointed out, it erases all the tx information with the rx information.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A faulty Linux Qualcomm SoundWire change can corrupt kernel memory and crash affected systems during audio-device initialization. Dragonboard 845c is confirmed to panic. The source assigns CVSS 7.8, but it does not demonstrate data theft or remote compromise.

Executive priority

Treat as a high-priority stability and kernel-integrity issue for exposed Qualcomm-based systems. Patch confirmed Dragonboard 845c or SDM845 deployments promptly, then assess other Qualcomm SoundWire devices. Broader emergency response is not supported because exposure is hardware-path dependent and active exploitation is not documented.

Technical view

The set_channel_map implementation writes an unused configuration element, can exceed the pconfig array, and overwrites transmit information with receive information. The out-of-bounds behavior can corrupt kernel memory; the documented failure is an EL1 exception followed by a fatal kernel panic. The resolution reverts commit 7796c97df6b1b2206681a07f3c80f6023a6593d5.

Likely exposure

Exposure appears limited to kernels containing the faulty commit and systems using the affected Qualcomm SoundWire path. Dragonboard 845c with SDM845 is explicitly confirmed. The bundle lists Linux 6.15-related and 6.16 version data, but its exact range encoding is ambiguous; verify vendor kernel ancestry rather than relying solely on version numbers.

Exploitation context

CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. CVSS describes a local, low-complexity attack requiring low privileges and no user interaction. However, the public description documents defects and a panic, not a proven privilege-escalation technique; practical exploitability beyond denial of service remains unestablished.

Researcher notes

The strongest evidence is an array-size mismatch causing memory corruption, plus incorrect index and state-overwrite defects. CVSS claims high confidentiality, integrity, and availability impact, while the description directly demonstrates availability loss only. The affected-version metadata is unclear, so commit-level verification is preferable. No CWE is supplied.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the referenced upstream or stable revert.
  • Confirm the faulty commit is absent or reverted in custom and downstream kernels.
  • Prioritize Qualcomm SoundWire systems, especially Dragonboard 845c or SDM845 deployments.
  • If updates are unavailable, obtain platform-specific mitigation guidance from the kernel or device vendor.

Validation and detection

  • Check kernel source or vendor advisories for the faulty commit and its revert.
  • Inventory systems using Qualcomm SoundWire drivers and affected kernel builds.
  • Test audio-device initialization safely in staging and monitor for kernel exceptions or panics.
  • Confirm the corrected kernel boots and initializes SoundWire audio without regressions.
Prepared
Confidence
medium
Sources
4

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-38486 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38486Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
LinuxLinux7796c97df6b1b2206681a07f3c80f6023a6593d5, 7796c97df6b1b2206681a07f3c80f6023a6593d5unaffected
LinuxLinux6.15, 0, 6.15.8, 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.