CVE-2026-90348: wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 045d1bfb72d2631ab9ec74afa491aa788ebb57aa, 152e894e90716163c646d70f86b3afeb70442783, 4f25071afe9218aaae1c63fbf75e229aa6405319.
Low priority for now. Upgrade to Linux Linux 045d1bfb72d2631ab9ec74afa491aa788ebb57aa, 152e894e90716163c646d70f86b3afeb70442783, 4f25071afe9218aaae1c63fbf75e229aa6405319 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.5affected
- 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and later · before e5bc3658da9c8a535e3fa5c0c875b2a456954e81affected · git
- 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and later · before fed1f662c9f9fd19eeab6c01966b7b5a33804420affected · git
- 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and later · before 838cab267ce9a975776e022f25094f8cbe1625d2affected · git
- 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and later · before eb946595a58decdb4cab1b5f3c972ae66f41f1c8affected · git
- 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and later · before 152e894e90716163c646d70f86b3afeb70442783affected · git
- 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and later · before 7039825a7479df637c4f5d546cb0e1cec18cd8e1affected · git
- 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and later · before 045d1bfb72d2631ab9ec74afa491aa788ebb57aaaffected · git
- 3f14b73c38431a6a1ed24de568e18ed89b7082e2 and later · before 4f25071afe9218aaae1c63fbf75e229aa6405319affected · git
- before 5.5not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90346Sep 17, 2026 · wifi: nl80211: clean up color-change beacon data on errors0Monitor
- ← EarlierCVE-2026-90347Sep 17, 2026 · arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry33Monitor
- Later →CVE-2026-90349Sep 17, 2026 · wifi: mt76: mt7996: fix out-of-bounds link array access in mt7996_tx()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 045d1bfb72d2631ab9ec74afa491aa788ebb57aa | Vendor (CNA) |
| Linux Linux | 152e894e90716163c646d70f86b3afeb70442783 | Vendor (CNA) |
| Linux Linux | 4f25071afe9218aaae1c63fbf75e229aa6405319 | Vendor (CNA) |
| Linux Linux | 7039825a7479df637c4f5d546cb0e1cec18cd8e1 | Vendor (CNA) |
| Linux Linux | 838cab267ce9a975776e022f25094f8cbe1625d2 | Vendor (CNA) |
| Linux Linux | e5bc3658da9c8a535e3fa5c0c875b2a456954e81 | Vendor (CNA) |
| Linux Linux | eb946595a58decdb4cab1b5f3c972ae66f41f1c8 | Vendor (CNA) |
| Linux Linux | fed1f662c9f9fd19eeab6c01966b7b5a33804420 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/152e894e90716163c646d70f86b3afeb70442783
- git.kernel.org/stable/c/4f25071afe9218aaae1c63fbf75e229aa6405319
- git.kernel.org/stable/c/7039825a7479df637c4f5d546cb0e1cec18cd8e1
- git.kernel.org/stable/c/838cab267ce9a975776e022f25094f8cbe1625d2
- git.kernel.org/stable/c/e5bc3658da9c8a535e3fa5c0c875b2a456954e81
- git.kernel.org/stable/c/eb946595a58decdb4cab1b5f3c972ae66f41f1c8
- git.kernel.org/stable/c/fed1f662c9f9fd19eeab6c01966b7b5a33804420
Vendor advisories and official records. Exploit/PoC links are deliberately left out.