CVE-2026-90348 — wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump
In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump On WCN3990/SNOC the MSA region is mapped with devm_memremap(MEMREMAP_WT). On arm64 such a mapping is not Normal-cacheable, so unaligned accesses to it are not permitted. ath10k_msa_dump_memory() copies the region with a plain memcpy(), whose optimized __pi_memcpy_generic implementation issues wide/unaligned loads. This triggers an alignment fault (FSC=0x21) Oops in ath10k_snoc_fw_crashed_dump() while collecting the devcoredump: Unable to handle kernel paging request ... FSC=0x21: alignment fault pc : __pi_memcpy_generic lr : ath10k_snoc_fw_crashed_dump [ath10k_snoc] The Oops both leaves the firmware RAM dump buffer zeroed (no dump is captured) and crashes the kernel, which in turn breaks modem SSR recovery. Use memcpy_fromio(), which only performs accesses that are valid for such a device-memory mapping. The generic memcpy_fromio() implementation aligns the source before issuing word-sized reads and stores the destination with put_unaligned(), so it is also safe for the coherent DMA allocation used on the non-reserved-memory path. ath11k and ath12k use the same pattern when copying target memory into crash dumps, so call it unconditionally here too. The MEMREMAP_WT pointer is a plain void *, so an explicit __iomem cast is needed; use __force to keep sparse happy. Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.3.3.7.c5-00107-QCAHLSWMTPL-1
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and < e5bc3658da9c8a535e3fa5c0c875b2a456954e81≥ 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and < fed1f662c9f9fd19eeab6c01966b7b5a33804420≥ 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and < 838cab267ce9a975776e022f25094f8cbe1625d2≥ 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and < eb946595a58decdb4cab1b5f3c972ae66f41f1c8≥ 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and < 152e894e90716163c646d70f86b3afeb70442783≥ 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and < 7039825a7479df637c4f5d546cb0e1cec18cd8e1≥ 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and < 045d1bfb72d2631ab9ec74afa491aa788ebb57aa≥ 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and < 4f25071afe9218aaae1c63fbf75e229aa6405319 and 1 moreversion 5.5 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 18, 2026 · 3 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/4f25071afe9218aaae1c63fbf75e229aa6405319
- git.kernel.org/stable/c/152e894e90716163c646d70f86b3afeb70442783
- git.kernel.org/stable/c/7039825a7479df637c4f5d546cb0e1cec18cd8e1
- git.kernel.org/stable/c/e5bc3658da9c8a535e3fa5c0c875b2a456954e81
- git.kernel.org/stable/c/eb946595a58decdb4cab1b5f3c972ae66f41f1c8
- git.kernel.org/stable/c/045d1bfb72d2631ab9ec74afa491aa788ebb57aa
- git.kernel.org/stable/c/fed1f662c9f9fd19eeab6c01966b7b5a33804420
- git.kernel.org/stable/c/838cab267ce9a975776e022f25094f8cbe1625d2
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 14h
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 14h
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 14h
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 14h
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 14h
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 14h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90348 is "wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.