cve.bz

CVE-2022-50880 linux linux

8.8 highEPSS 0.3%Fix available

High (8.8) in linux linux. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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---

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 4.9.331
  • Linux Linux: fixed in 4.14.296
  • Linux Linux: fixed in 4.19.262
  • Linux Linux: fixed in 5.4.220
  • Linux Linux: fixed in 5.10.150
  • Linux Linux: fixed in 5.15.75
  • Linux Linux: fixed in 5.19.17
  • Linux Linux: fixed in 6.0.3
  • Debian, Ubuntu, SUSE: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2022-50880 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-50880?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-50880?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-50880 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2022-50880

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2022-50880](https://cve.bz/cve/badge/CVE-2022-50880.svg)](https://cve.bz/cve/CVE-2022-50880)

HTML:

<a href="https://cve.bz/cve/CVE-2022-50880"><img src="https://cve.bz/cve/badge/CVE-2022-50880.svg" alt="CVE-2022-50880"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.8 and later

Fixed in

ProductRelease lineFixed in
Linux4.94.9.331
Linux4.144.14.296
Linux4.194.19.262
Linux5.45.4.220
Linux5.105.10.150
Linux5.155.15.75
Linux5.195.19.17
Linux6.06.0.3
Linuxlater releases6.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14linux6.0.3-1DEBIAN-CVE-2022-50880
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux4.15.0-204.215UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-aws4.15.0-1150.163UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-aws-5.45.4.0-1096.104~18.04.1UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-azure-4.154.15.0-1161.176UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-azure-5.45.4.0-1103.109~18.04.1UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-gcp-4.154.15.0-1145.161UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-gcp-5.45.4.0-1100.109~18.04.1UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-hwe-5.45.4.0-139.156~18.04.1UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-ibm-5.45.4.0-1044.49~18.04.1UBUNTU-CVE-2022-50880
Ubuntu18.04:LTSlinux-kvm4.15.0-1135.140UBUNTU-CVE-2022-50880
53 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP4, Linux Enterprise Live Patching 15 SP4, Linux Enterprise Micro 5.3 and 1 morekernel-default5.14.21-150400.24.194.1SUSE-SU-2026:0617-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150400.24.194.1SUSE-SU-2026:0617-1
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise Micro 5.3 and 3 morekernel-default-base5.14.21-150400.24.194.1.150400.24.98.3SUSE-SU-2026:0617-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSSkernel-64kb, kernel-docs, kernel-syms and 3 more5.14.21-150500.55.133.1SUSE-SU-2026:0317-1
SUSELinux Enterprise High Performance Computing 15 SP5-ESPOS, Linux Enterprise High Performance Computing 15 SP5-LTSS, Linux Enterprise Micro 5.5 and 2 morekernel-default-base5.14.21-150500.55.133.1.150500.6.65.1SUSE-SU-2026:0317-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.293.1SUSE-SU-2026:0473-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_771-8.3.1SUSE-SU-2026:0473-1
SUSELinux Enterprise Live Patching 15 SP4kernel-livepatch-SLE15-SP4_Update_481-150400.9.7.1SUSE-SU-2026:0617-1
SUSELinux Enterprise Live Patching 15 SP5kernel-default5.14.21-150500.55.133.1SUSE-SU-2026:0317-1
SUSELinux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_341-150500.11.3.1SUSE-SU-2026:0317-1
SUSELinux Enterprise Micro 5.2kernel-default5.3.18-150300.59.232.1SUSE-SU-2026:0369-1
SUSELinux Enterprise Micro 5.2kernel-default-base5.3.18-150300.59.232.1.150300.18.138.1SUSE-SU-2026:0369-1
9 more for SUSE in the JSON and on SUSE's page.

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A use-after-free vulnerability exists in the ath10k Wi-Fi driver when multiple peer IDs in peer_map[] reference the same ath10k_peer object. If firmware peer deletion fails during disconnect, the driver may free the peer while leaving stale references, leading to a UAF read in ath10k_sta_state() and a kernel crash. Exploitability is typically constrained by firmware-dependent behavior and timing, making reliable remote exploitation difficult in practice, with DoS being the most realistic outcome.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-50880.

References

Check your stackJSON