CVE-2022-50665

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-12-09. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2022-55740 (ENISA EUVD) · GHSA-ppjq-9892-q46w (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: ath11k: fix failed to find the peer with peer_id 0 when disconnected

It has a fail log which is ath11k_dbg in ath11k_dp_rx_process_mon_status(), as below, it will not print when debug_mask is not set ATH11K_DBG_DATA. ath11k_dbg(ab, ATH11K_DBG_DATA, "failed to find the peer with peer_id %d\n", ppdu_info.peer_id);

When run scan with station disconnected, the peer_id is 0 for case HAL_RX_MPDU_START in ath11k_hal_rx_parse_mon_status_tlv() which called from ath11k_dp_rx_process_mon_status(), and the peer_id of ppdu_info is reset to 0 in the while loop, so it does not match condition of the check "if (ppdu_info->peer_id == HAL_INVALID_PEERID" in the loop, and then the log "failed to find the peer with peer_id 0" print after the check in the loop, it is below call stack when debug_mask is set ATH11K_DBG_DATA.

The reason is this commit 01d2f285e3e5 ("ath11k: decode HE status tlv") add "memset(ppdu_info, 0, sizeof(struct hal_rx_mon_ppdu_info))" in ath11k_dp_rx_process_mon_status(), but the commit does not initialize the peer_id to HAL_INVALID_PEERID, then lead the check mis-match.

Callstack of the failed log: [12335.689072] RIP: 0010:ath11k_dp_rx_process_mon_status+0x9ea/0x1020 [ath11k] [12335.689157] Code: 89 ff e8 f9 10 00 00 be 01 00 00 00 4c 89 f7 e8 dc 4b 4e de 48 8b 85 38 ff ff ff c7 80 e4 07 00 00 01 00 00 00 e9 20 f8 ff ff <0f> 0b 41 0f b7 96 be 06 00 00 48 c7 c6 b8 50 44 c1 4c 89 ff e8 fd [12335.689180] RSP: 0018:ffffb874001a4ca0 EFLAGS: 00010246 [12335.689210] RAX: 0000000000000000 RBX: ffff995642cbd100 RCX: 0000000000000000 [12335.689229] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff99564212cd18 [12335.689248] RBP: ffffb874001a4dc0 R08: 0000000000000001 R09: 0000000000000000 [12335.689268] R10: 0000000000000220 R11: ffffb874001a48e8 R12: ffff995642473d40 [12335.689286] R13: ffff99564212c5b8 R14: ffff9956424736a0 R15: ffff995642120000 [12335.689303] FS: 0000000000000000(0000) GS:ffff995739000000(0000) knlGS:0000000000000000 [12335.689323] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [12335.689341] CR2: 00007f43c5d5e039 CR3: 000000011c012005 CR4: 00000000000606e0 [12335.689360] Call Trace: [12335.689377] [12335.689418] ? rcu_read_lock_held_common+0x12/0x50 [12335.689447] ? rcu_read_lock_sched_held+0x25/0x80 [12335.689471] ? rcu_read_lock_held_common+0x12/0x50 [12335.689504] ath11k_dp_rx_process_mon_rings+0x8d/0x4f0 [ath11k] [12335.689578] ? ath11k_dp_rx_process_mon_rings+0x8d/0x4f0 [ath11k] [12335.689653] ? lock_acquire+0xef/0x360 [12335.689681] ? rcu_read_lock_sched_held+0x25/0x80 [12335.689713] ath11k_dp_service_mon_ring+0x38/0x60 [ath11k] [12335.689784] ? ath11k_dp_rx_process_mon_rings+0x4f0/0x4f0 [ath11k] [12335.689860] call_timer_fn+0xb2/0x2f0 [12335.689897] ? ath11k_dp_rx_process_mon_rings+0x4f0/0x4f0 [ath11k] [12335.689970] run_timer_softirq+0x21f/0x540 [12335.689999] ? ktime_get+0xad/0x160 [12335.690025] ? lapic_next_deadline+0x2c/0x40 [12335.690053] ? clockevents_program_event+0x82/0x100 [12335.690093] __do_softirq+0x151/0x4a8 [12335.690135] irq_exit_rcu+0xc9/0x100 [12335.690165] sysvec_apic_timer_interrupt+0xa8/0xd0 [12335.690189] [12335.690204] [12335.690225] asm_sysvec_apic_timer_interrupt+0x12/0x20

Reset the default value to HAL_INVALID_PEERID each time after memset of ppdu_info as well as others memset which existed in function ath11k_dp_rx_process_mon_status(), then the failed log disappeared.

Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-04). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 9, 2025

Last Modified

October 15, 2026

Advisory Details (3)

Auto-updated Aug 8, 2026
Patch available.
Web page

wifi: ath11k: fix failed to find the peer with peer_id 0 when disconnected - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a20ed60bb357776301c2dad7b4a4f0db97e143e9
Web page

wifi: ath11k: fix failed to find the peer with peer_id 0 when disconnected - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a5b03df19041e5ce35c7f048fa84bf1b0ceb1311
Web page

wifi: ath11k: fix failed to find the peer with peer_id 0 when disconnected - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c0bb97a90b133416b50b3ffbdb7efca9253cc687

Vendor Advisories for CVE-2022-50665(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 / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.19.17 (fixes >=5.18.0)—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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 252 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 153 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-50665?
CVE-2022-50665 is a high-severity vulnerability; its CVE record was published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix failed to find the peer with peer_id 0 when disconnected It has a fail log which is ath11k_dbg in ath11k_dp_rx_process_mon_status(), as below, it will not print when debug_mask is not set ATH11K_DBG_DATA.…
When was the CVE record for CVE-2022-50665 published?
The CVE record for CVE-2022-50665 was published on December 9, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2022-50665 actively exploited?
CVE-2022-50665 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50665?
CVE-2022-50665 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2022-50665?
A fix for CVE-2022-50665 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50665 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-50665?

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

Book a Demo →Browse All CVEs