LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49533: ath11k: Change max no of active probe SSID and BSSID to fw capability

In the Linux kernel, the following vulnerability has been resolved: ath11k: Change max no of active probe SSID and BSSID to fw capability The maximum number of SSIDs in a for active probe requests is currently reported as 16 (WLAN_SCAN_PARAMS_MAX_SSID) when registering the driver. The scan_req_params structure only has the capacity to hold 10 SSIDs. This leads to a buffer overflow which can be triggered from wpa_supplicant in userspace. When copying the SSIDs into the scan_req_params structure in the ath11k_mac_op_hw_scan route, it can overwrite the extraie pointer. Firmware supports 16 ssid * 4 bssid, for each ssid 4 bssid combo probe request will be sent, so totally 64 probe requests supported. So set both max ssid and bssid to 16 and 4 respectively. Remove the redundant macros of ssid and bssid. Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.7.0.1-01300-QCAHKSWPL_SILICONZ-1

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-49533 is a Linux kernel ath11k Wi-Fi driver flaw. The driver advertised support for more active probe SSIDs than an internal scan structure could hold, causing a buffer overflow reachable from wpa_supplicant. Business impact depends on whether affected Linux systems use ath11k wireless hardware.

Executive priority

Treat as a targeted Linux endpoint and appliance remediation item, not a broad enterprise emergency. Prioritize wireless-enabled Linux fleets, embedded devices, and edge systems using ath11k hardware.

Technical view

In ath11k_mac_op_hw_scan, copying user-space scan SSIDs into scan_req_params could exceed the structure’s 10-SSID capacity because the driver reported 16. The overflow could overwrite the extraie pointer. Kernel stable fixes align maximum SSID and BSSID values with firmware capability.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions with the ath11k wireless driver and compatible Qualcomm wireless hardware enabled. Servers without ath11k Wi-Fi are unlikely to be exposed.

Exploitation context

The source states the overflow can be triggered from wpa_supplicant in userspace. The bundle does not report public exploitation, KEV listing, exploit availability, CVSS score, or proven impact beyond memory corruption.

Researcher notes

The CVE record provides a clear root cause and stable fix references, but lacks CVSS, CWE, exploit status, and full affected-version precision. Avoid assuming remote exploitability or privilege-escalation impact without additional vendor evidence.

Mitigation direction

  • Update to a kernel or distro package containing the referenced stable fixes.
  • Check Linux distribution advisories for exact fixed package versions.
  • Disable or remove ath11k wireless support where Wi-Fi is unnecessary.
  • Prioritize systems where local users can influence wireless scanning behavior.

Validation and detection

  • Inventory systems using affected Linux kernel versions and ath11k wireless hardware.
  • Confirm whether ath11k is loaded or packaged for target devices.
  • Verify installed kernel packages include the referenced stable fixes.
  • Review wireless client configurations that rely on wpa_supplicant scanning.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2022-49533 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd5c65159f2895379e11ca13f62feabe93278985d, d5c65159f2895379e11ca13f62feabe93278985d, d5c65159f2895379e11ca13f62feabe93278985dunaffected
LinuxLinux5.6, 0, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.