Kernel crash via stale ath10k peer mapping
Published Dec 30, 2025 · Updated Dec 30, 2025
Use-after-free in the Linux kernel ath10k driver allows physically proximate attackers to crash or hang systems during Wi-Fi disconnects. Multiple firmware peer-map identifiers can reference one ath10k_peer, but failed deletion frees that shared object while later identifiers still reference it. Reachability requires an ath10k connection and an adjacent Wi-Fi disconnection trigger; the resulting stale access can corrupt kernel memory and interrupt the host.
Summary
What happened
Use-after-free in the Linux kernel ath10k driver allows physically proximate attackers to crash or hang systems during Wi-Fi disconnects. Multiple firmware peer-map identifiers can reference one ath10k_peer, but failed deletion frees that shared object while later identifiers still reference it. Reachability requires an ath10k connection and an adjacent Wi-Fi disconnection trigger; the resulting stale access can corrupt kernel memory and interrupt the host.
The record
- CVE
- CVE-2022-50880
- Published
- Dec 30, 2025
- Updated
- Dec 30, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 30, 2025CVE publishedPublication date reported by the CVE source.
- Dec 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.8
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <08faf07717be0c88b02b5aa45aad2225dfcdd2dc
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <15604ab67179ae27ea3c7fb24b6df32b143257c4
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <2bf916418d2141b810c40812433ab4ecfd3c2934
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <2d6259715c9597a6cfa25db8911683eb0073b1c6
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <38245f2d62cd4d1f38a763a7b4045ab4565b30a0
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <4494ec1c0bb850eaa80fed98e5b041d961011d3e
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <54a3201f3c1ff813523937da78b5fa7649dbab71
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <f020d9570a04df0762a2ac5c50cf1d8c511c9164
- Affected versionversion=d0eeafad118940fe445ca00f45be5624fea2ec34 <f12fc305c127bd07bb50373e29c6037696f916a8
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo