CVE-2026-90348

CVE CVE-2026-90348EUVD EUVD-2026-82009Published 2026-09-17T16:08:56.000Z

What the advisory describes

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

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 3f14b73c38431a6a1ed24de568e18ed89b7082e2 <045d1bfb72d2631ab9ec74afa491aa788ebb57aa; 3f14b73c38431a6a1ed24de568e18ed89b7082e2 <152e894e90716163c646d70f86b3afeb70442783; 3f14b73c38431a6a1ed24de568e18ed89b7082e2 <838cab267ce9a975776e022f25094f8cbe1625d2; 3f14b73c38431a6a1ed24de568e18ed89b7082e2 <fed1f662c9f9fd19eeab6c01966b7b5a33804420; patch: 6.6.157; patch: 5.15.221; 3f14b73c38431a6a1ed24de568e18ed89b7082e2 <eb946595a58decdb4cab1b5f3c972ae66f41f1c8; patch: 6.18.52; patch: 0; patch: 7.2.6; patch: 6.12.110; patch: 6.1.188; 3f14b73c38431a6a1ed24de568e18ed89b7082e2 <4f25071afe9218aaae1c63fbf75e229aa6405319; 5.5; patch: 5.10.270; 3f14b73c38431a6a1ed24de568e18ed89b7082e2 <e5bc3658da9c8a535e3fa5c0c875b2a456954e81; 3f14b73c38431a6a1ed24de568e18ed89b7082e2 <7039825a7479df637c4f5d546cb0e1cec18cd8e1; patch: 7.3-rc1

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.