CVE-2022-50880

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-30. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state()

When peer delete failed in a disconnect operation, use-after-free detected by KFENCE in below log. It is because for each vdev_id and address, it has only one struct ath10k_peer, it is allocated in ath10k_peer_map_event(). When connected to an AP, it has more than one HTT_T2H_MSG_TYPE_PEER_MAP reported from firmware, then the array peer_map of struct ath10k will be set muti-elements to the same ath10k_peer in ath10k_peer_map_event(). When peer delete failed in ath10k_sta_state(), the ath10k_peer will be free for the 1st peer id in array peer_map of struct ath10k, and then use-after-free happened for the 2nd peer id because they map to the same ath10k_peer.

And clean up all peers in array peer_map for the ath10k_peer, then user-after-free disappeared

peer map event log: [ 306.911021] wlan0: authenticate with b0:2a:43:e6:75:0e [ 306.957187] ath10k_pci 0000:01:00.0: mac vdev 0 peer create b0:2a:43:e6:75:0e (new sta) sta 1 / 32 peer 1 / 33 [ 306.957395] ath10k_pci 0000:01:00.0: htt peer map vdev 0 peer b0:2a:43:e6:75:0e id 246 [ 306.957404] ath10k_pci 0000:01:00.0: htt peer map vdev 0 peer b0:2a:43:e6:75:0e id 198 [ 306.986924] ath10k_pci 0000:01:00.0: htt peer map vdev 0 peer b0:2a:43:e6:75:0e id 166

peer unmap event log: [ 435.715691] wlan0: deauthenticating from b0:2a:43:e6:75:0e by local choice (Reason: 3=DEAUTH_LEAVING) [ 435.716802] ath10k_pci 0000:01:00.0: mac vdev 0 peer delete b0:2a:43:e6:75:0e sta ffff990e0e9c2b50 (sta gone) [ 435.717177] ath10k_pci 0000:01:00.0: htt peer unmap vdev 0 peer b0:2a:43:e6:75:0e id 246 [ 435.717186] ath10k_pci 0000:01:00.0: htt peer unmap vdev 0 peer b0:2a:43:e6:75:0e id 198 [ 435.717193] ath10k_pci 0000:01:00.0: htt peer unmap vdev 0 peer b0:2a:43:e6:75:0e id 166

use-after-free log: [21705.888627] wlan0: deauthenticating from d0:76:8f:82:be:75 by local choice (Reason: 3=DEAUTH_LEAVING) [21713.799910] ath10k_pci 0000:01:00.0: failed to delete peer d0:76:8f:82:be:75 for vdev 0: -110 [21713.799925] ath10k_pci 0000:01:00.0: found sta peer d0:76:8f:82:be:75 (ptr 0000000000000000 id 102) entry on vdev 0 after it was supposedly removed [21713.799968] ================================================================== [21713.799991] BUG: KFENCE: use-after-free read in ath10k_sta_state+0x265/0xb8a [ath10k_core] [21713.799991] [21713.799997] Use-after-free read at 0x00000000abe1c75e (in kfence-#69): [21713.800010] ath10k_sta_state+0x265/0xb8a [ath10k_core] [21713.800041] drv_sta_state+0x115/0x677 [mac80211] [21713.800059] __sta_info_destroy_part2+0xb1/0x133 [mac80211] [21713.800076] __sta_info_flush+0x11d/0x162 [mac80211] [21713.800093] ieee80211_set_disassoc+0x12d/0x2f4 [mac80211] [21713.800110] ieee80211_mgd_deauth+0x26c/0x29b [mac80211] [21713.800137] cfg80211_mlme_deauth+0x13f/0x1bb [cfg80211] [21713.800153] nl80211_deauthenticate+0xf8/0x121 [cfg80211] [21713.800161] genl_rcv_msg+0x38e/0x3be [21713.800166] netlink_rcv_skb+0x89/0xf7 [21713.800171] genl_rcv+0x28/0x36 [21713.800176] netlink_unicast+0x179/0x24b [21713.800181] netlink_sendmsg+0x3a0/0x40e [21713.800187] sock_sendmsg+0x72/0x76 [21713.800192] ____sys_sendmsg+0x16d/0x1e3 [21713.800196] ___sys_sendmsg+0x95/0xd1 [21713.800200] __sys_sendmsg+0x85/0xbf [21713.800205] do_syscall_64+0x43/0x55 [21713.800210] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [21713.800213] [21713.800219] kfence-#69: 0x000000009149b0d5-0x000000004c0697fb, size=1064, cache=kmalloc-2k [21713.800219] [21713.800224] allocated by task 13 on cpu 0 at 21705.501373s: [21713.800241] ath10k_peer_map_event+0x7e/0x154 [ath10k_core] [21713.800254] ath10k_htt_t2h_msg_handler+0x586/0x1039 [ath10k_core] [21713.800265] ath10k_htt_htc_t2h_msg_handler+0x12/0x28 [ath10k_core] [21713.800277] ath10k_htc_rx_completion_handler+0x14c/0x1b5 [ath10k_core] [21713.800283] ath10k_pci_process_rx_cb+0x195/0x1d ---truncated---

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

December 30, 2025

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f020d9570a04df0762a2ac5c50cf1d8c511c9164
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38245f2d62cd4d1f38a763a7b4045ab4565b30a0
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2bf916418d2141b810c40812433ab4ecfd3c2934
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54a3201f3c1ff813523937da78b5fa7649dbab71
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08faf07717be0c88b02b5aa45aad2225dfcdd2dc
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4494ec1c0bb850eaa80fed98e5b041d961011d3e
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f12fc305c127bd07bb50373e29c6037696f916a8
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d6259715c9597a6cfa25db8911683eb0073b1c6
generic

wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15604ab67179ae27ea3c7fb24b6df32b143257c4

Vendor Advisories for CVE-2022-50880(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.9.331—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (22 versions)5.10.158-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.3-1—

Data Freshness Timeline

(refreshed 4× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-09-20 20:13 UTCEPSS rescore
  2. 2026-09-19 21:52 UTCOSV refresh
  3. 2026-09-16 14:05 UTCEPSS rescore
  4. 2026-09-16 05:11 UTCEPSS rescore
  5. 2026-09-15 03:07 UTCEPSS rescore
  6. 2026-09-13 16:44 UTCEPSS rescore
  7. 2026-09-11 14:50 UTCEPSS rescore
  8. 2026-09-11 09:34 UTCEPSS rescore
  9. 2026-09-08 21:57 UTCEPSS rescore
  10. 2026-09-06 13:45 UTCEPSS rescore
  11. 2026-09-05 15:25 UTCEPSS rescore
  12. 2026-09-04 13:57 UTCEPSS rescore
  13. 2026-09-04 05:04 UTCEPSS rescore
  14. 2026-09-02 14:09 UTCEPSS rescore
  15. 2026-09-01 13:51 UTCEPSS rescore
  16. 2026-09-01 01:34 UTCOSV refresh
  17. 2026-08-30 19:15 UTCEPSS rescore
  18. 2026-08-30 01:19 UTCEPSS rescore
  19. 2026-08-28 21:38 UTCEPSS rescore
  20. 2026-08-27 14:22 UTCEPSS rescore
  21. 2026-08-26 14:43 UTCEPSS rescore
  22. 2026-08-25 13:46 UTCEPSS rescore
  23. 2026-08-23 00:17 UTCEPSS rescore
  24. 2026-08-21 23:46 UTCEPSS rescore
  25. 2026-08-20 22:53 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:01 UTCEPSS rescore
  2. 2026-08-18 13:45 UTCEPSS rescore
  3. 2026-08-17 13:44 UTCEPSS rescore
  4. 2026-08-16 14:53 UTCEPSS rescore
  5. 2026-08-16 02:12 UTCEPSS rescore
  6. 2026-08-15 01:27 UTCEPSS rescore
  7. 2026-08-15 01:20 UTCEG score recompute
  8. 2026-08-15 01:20 UTCGHSA enrichment
  9. 2026-08-13 21:58 UTCEPSS rescore
  10. 2026-08-12 13:48 UTCEPSS rescore
  11. 2026-08-09 22:25 UTCEG score recompute
  12. 2026-08-09 22:25 UTCGHSA enrichment
  13. 2026-08-09 13:44 UTCEPSS rescore
  14. 2026-08-09 13:44 UTCEPSS rescore
  15. 2026-08-08 04:36 UTCEG score recompute
  16. 2026-08-08 04:36 UTCGHSA enrichment
  17. 2026-08-07 16:24 UTCEPSS rescore
  18. 2026-08-06 13:44 UTCEPSS rescore
  19. 2026-08-06 06:47 UTCEG score recompute
  20. 2026-08-06 06:47 UTCGHSA enrichment
  21. 2026-08-05 19:15 UTCEPSS rescore
  22. 2026-08-05 09:16 UTCEG score recompute
  23. 2026-08-05 09:16 UTCGHSA enrichment
  24. 2026-08-04 15:07 UTCEPSS rescore
  25. 2026-08-04 10:35 UTCEPSS rescore
  26. 2026-08-04 10:32 UTCEG score recompute
  27. 2026-08-04 10:31 UTCGHSA enrichment
  28. 2026-08-04 09:21 UTCEG score recompute▲ 8.80
  29. 2026-08-04 09:21 UTCGHSA enrichment
  30. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  31. 2026-08-03 10:33 UTCEPSS rescore
  32. 2026-08-02 02:24 UTCEPSS rescore
  33. 2026-08-01 04:13 UTCEPSS rescore
  34. 2026-08-01 04:13 UTCEPSS rescore
  35. 2026-07-30 16:25 UTCEPSS rescore
  36. 2026-07-30 01:28 UTCEPSS rescore
  37. 2026-07-28 15:34 UTCEPSS rescore
  38. 2026-07-27 03:09 UTCOSV refresh
  39. 2026-07-26 14:52 UTCEPSS rescore
  40. 2026-07-26 14:52 UTCEPSS rescore
  41. 2026-07-25 14:16 UTCEPSS rescore
  42. 2026-07-24 14:15 UTCEPSS rescore
  43. 2026-07-23 14:16 UTCEPSS rescore
  44. 2026-07-23 14:16 UTCEPSS rescore
  45. 2026-07-23 02:17 UTCEG score recompute
  46. 2026-07-22 23:04 UTCEG score recompute
  47. 2026-07-22 14:06 UTCEPSS rescore
  48. 2026-07-22 14:06 UTCEPSS rescore
  49. 2026-07-21 15:23 UTCEPSS rescore
  50. 2026-07-21 15:23 UTCEPSS rescore
  51. 2026-07-20 17:05 UTCEPSS rescore
  52. 2026-07-19 14:29 UTCEPSS rescore
  53. 2026-07-19 14:29 UTCEPSS rescore
  54. 2026-07-19 02:27 UTCEPSS rescore
  55. 2026-07-19 02:27 UTCEPSS rescore
  56. 2026-07-18 10:03 UTCEPSS rescore
  57. 2026-07-18 10:03 UTCEPSS rescore
  58. 2026-07-16 17:00 UTCEPSS rescore
  59. 2026-07-15 16:56 UTCEPSS rescore
  60. 2026-07-15 16:56 UTCEPSS rescore
  61. 2026-07-15 01:58 UTCEPSS rescore
  62. 2026-07-15 01:58 UTCEPSS rescore
  63. 2026-07-13 22:28 UTCEPSS rescore
  64. 2026-07-13 22:28 UTCEPSS rescore
  65. 2026-07-13 06:11 UTCEPSS rescore
  66. 2026-07-13 06:11 UTCEPSS rescore
  67. 2026-07-12 05:44 UTCEPSS rescore
  68. 2026-07-11 08:25 UTCEPSS rescore
  69. 2026-07-11 08:25 UTCEPSS rescore
  70. 2026-07-09 21:17 UTCOSV refresh
  71. 2026-07-09 19:08 UTCEPSS rescore
  72. 2026-07-08 15:13 UTCEPSS rescore
  73. 2026-07-07 13:44 UTCEPSS rescore
  74. 2026-07-06 16:25 UTCEPSS rescore
  75. 2026-07-06 02:21 UTCEPSS rescore

Related CVEs(same product)

Frequently asked(5)

What is CVE-2022-50880?
CVE-2022-50880 is a high vulnerability published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: add peer map clean up for peer delete in ath10kstastate() When peer delete failed in a disconnect operation, use-after-free detected by KFENCE in below log. It is because for each vdev_id and address, it has only one…
When was CVE-2022-50880 disclosed?
CVE-2022-50880 was first published in the National Vulnerability Database on December 30, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50880 actively exploited?
CVE-2022-50880 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.8% of all scored CVEs.
What is the CVSS score of CVE-2022-50880?
CVE-2022-50880 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-50880?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50880, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50880

Explore →

Is Your Infrastructure Affected by CVE-2022-50880?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs