Security readout for executives and security teams
Plain-English summary
This is a Linux kernel ath11k Wi-Fi driver issue. When a disconnected station scans, peer tracking can be initialized incorrectly, producing a failure log and call trace under specific debug settings. Public sources do not provide CVSS, impact severity, or evidence of exploitation.
Executive priority
Treat as low urgency unless your fleet depends heavily on ath11k-based Wi-Fi endpoints. Patch through normal kernel maintenance after confirming vendor availability. There is no sourced evidence of active exploitation or severe business impact.
Technical view
In ath11k_dp_rx_process_mon_status(), ppdu_info was memset without resetting peer_id to HAL_INVALID_PEERID after commit 01d2f285e3e5. During monitor status parsing, peer_id 0 can bypass the invalid-peer check and trigger “failed to find the peer with peer_id 0.” Stable fixes reset peer_id after memset.
Likely exposure
Likely limited to Linux systems using the ath11k Qualcomm Wi-Fi driver, with affected kernel code and relevant scan/disconnected station conditions. The CVE notes testing on WCN6855 hardware, but does not define all affected devices.
Exploitation context
No KEV listing is indicated, and the provided sources do not claim active exploitation. The described condition appears operational and driver-specific, not a documented remote compromise path.
Researcher notes
The source record is unusually narrow and lacks CVSS, CWE, and impact analysis. The fix is a defensive initialization change in ath11k monitor status handling. Avoid assuming broader kernel compromise without additional vendor or maintainer evidence.
Mitigation direction
- Update to a kernel or vendor package containing the referenced stable ath11k fixes.
- Check Linux distribution advisories for backported fixes for CVE-2022-50665.
- Prioritize systems using ath11k Wi-Fi hardware over systems without this driver.
Validation and detection
- Inventory Linux systems with Qualcomm ath11k Wi-Fi hardware or loaded ath11k driver.
- Verify whether the running kernel includes the referenced stable fix commits.
- Review kernel logs for the cited peer_id 0 failure under ath11k debug conditions.
- Confirm vendor kernel changelogs mention CVE-2022-50665 or the ath11k peer_id fix.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2022-50665 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.