# CVE-2022-50871: wifi: ath11k: Fix qmi_msg_handler data structure initialization

> A missing null terminator in the ath11k WiFi driver can cause an infinite loop and out-of-bounds access, leading to a system crash.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2022-50871, GHSA-hvw4-g8mw-w34v, ROOT-OS-DEBIAN-11-CVE-2022-50871, ROOT-OS-UBUNTU-2204-CVE-2022-50871, UBUNTU-CVE-2022-50871

## What is CVE-2022-50871?

CVE-2022-50871 is a high-severity denial of service vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

wifi: ath11k: Fix qmi_msg_handler data structure initialization

qmi_msg_handler is required to be null terminated by QMI module.
There might be a case where a handler for a msg id is not present in the
handlers array which can lead to infinite loop while searching the handler
and therefore out of bound access in qmi_invoke_handler().
Hence update the initialization in qmi_msg_handler data structure.

Tested-on: IPQ8074 hw2.0 AHB WLAN.HK.2.5.0.1-01100-QCAHKSWPL_SILICONZ-1

## Which versions are affected by CVE-2022-50871?


## How do I fix CVE-2022-50871?

Apply the vendor's patch.

## Is CVE-2022-50871 being exploited?

There is no known exploitation of CVE-2022-50871 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50871 and fix it if it is affected.

What it is: CVE-2022-50871 is a high-severity denial of service vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50871 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-50871/ (Markdown: https://insights.sbomify.com/CVE-2022-50871/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50871
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50871
- OSV: https://osv.dev/vulnerability/CVE-2022-50871

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50871/
Summaries are generated and may contain mistakes; the official description above is the record.