CVE-2025-38649
arm64: dts: qcom: qcs615: fix a crash issue caused by infinite loop for Coresight
Reported by linux · Published August 22, 2025
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.
EPSS 0.19% · 8.9th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.16.1, 6.15.10 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | bf469630552a3950d0370dd5fd1f9bf0145d09d5, bf469630552a3950d0370dd5fd1f9bf0145d09d5, bf469630552a3950d0370dd5fd1f9bf0145d09d5 |
| Linux | Linux | 6.14, 0, 6.15.10 |
| linux | linux_kernel | 6.14, 6.14, 6.14 |
| Linux | Linux | *, *, 6.16.1 |
Timeline
- Aug 22, 2025 Coalition ESS Score (8 in total, the first dated here)
- Aug 22, 2025 CVE Published
- Aug 23, 2025 EPSS Score (30 in total, the first dated here)
- Dec 15, 2025 Security Advisory (186 in total, the first dated here)
- Dec 18, 2025 PoC Published (2 in total, the first dated here)
- Apr 20, 2026 Distribution Patch (138 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38649
vulnetix vdb fixes CVE-2025-38649
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38649/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart