CVE-2025-38649: arm64: dts: qcom: qcs615: fix a crash issue caused by infinite loop for Coresight
In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: qcom: qcs615: fix a crash issue caused by infinite loop for Coresight
An infinite loop has been created by the Coresight devices. When only a
source device is enabled, the coresight_find_activated_sysfs_sink function
is recursively invoked in an attempt to locate an active sink device,
ultimately leading to a stack overflow and system crash. Therefore, disable
the replicator1 to break the infinite loop and prevent a potential stack
overflow.
replicator1_out -> funnel_swao_in6 -> tmc_etf_swao_in -> tmc_etf_swao_out
| |
replicator1_in replicator_swao_in
| |
replicator0_out1 replicator_swao_out0
| |
replicator0_in funnel_in1_in3
| |
tmc_etf_out <- tmc_etf_in <- funnel_merg_out <- funnel_merg_in1 <- funnel_in1_out
[call trace]
dump_backtrace+0x9c/0x128
show_stack+0x20/0x38
dump_stack_lvl+0x48/0x60
dump_stack+0x18/0x28
panic+0x340/0x3b0
nmi_panic+0x94/0xa0
panic_bad_stack+0x114/0x138
handle_bad_stack+0x34/0xb8
__bad_stack+0x78/0x80
coresight_find_activated_sysfs_sink+0x28/0xa0 [coresight]
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
...
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
coresight_enable_sysfs+0x80/0x2a0 [coresight]
side effect after the change:
Only trace data originating from AOSS can reach the ETF_SWAO and EUD sinks.
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel crash issue on Qualcomm QCS615 arm64 device-tree Coresight wiring. A loop in trace-device relationships can cause recursive sink lookup until stack overflow and system crash. The source describes a fix that disables one replicator path to break the loop.
Executive priority
Prioritize affected embedded, mobile, edge, or appliance platforms using QCS615 where kernel crashes affect availability. This is not documented as remotely exploitable or actively exploited in the provided sources, so urgency should be driven by fleet presence and operational reliance on the affected hardware.
Technical view
When only a Coresight source device is enabled, coresight_find_activated_sysfs_sink can recursively follow the QCS615 Coresight topology until stack exhaustion. The kernel fix disables replicator1, preventing the infinite loop. The source notes a functional side effect: only AOSS-origin trace data can reach ETF_SWAO and EUD sinks.
Likely exposure
Exposure appears limited to Linux kernels with the affected QCS615 arm64 device-tree Coresight topology. The bundle lists affected kernel versions including 6.14, 6.15.10, 6.16.1, and 6.17, but does not map this to distributions, appliances, or cloud images.
Exploitation context
No source in the bundle reports active exploitation, and KEV is false. The described trigger is operational: enabling only a Coresight source device causes recursive lookup and a crash. Practical exposure likely depends on local access and Coresight sysfs/debug interface availability.
Researcher notes
The record lacks CVSS, CWE, distribution mapping, and exploitability detail. Treat this as a source-grounded kernel denial-of-service issue tied to a specific Coresight topology. Validate against exact kernel trees because vendors may backport the stable commits without changing the visible version string.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check vendor or distribution advisories for backported QCS615 Coresight fixes.
For custom kernels, confirm replicator1 is disabled as described upstream.
Limit untrusted access to Coresight debug and sysfs interfaces.
Assess the tracing side effect before deploying to diagnostic environments.
Validation and detection
Inventory systems using Qualcomm QCS615 and Linux arm64 kernels.
Compare running kernel versions against vendor-fixed builds or upstream stable commits.
For source builds, inspect the QCS615 device tree for the replicator1 change.
Review crash logs for repeated coresight_find_activated_sysfs_sink stack traces.
Confirm required Coresight tracing workflows still function after patching.
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-38649 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
4Source 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.
Aug 22, 2025, 16:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.