# CVE-2026-92497: wifi: ath12k: Avoid buffer overread in ath12k_wmi_op_rx()

> A buffer overread in the ath12k WiFi driver allows attackers to cause denial of service or leak kernel memory via crafted wireless frames.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102476, BELL-CVE-2026-92497, DEBIAN-CVE-2026-92497, GHSA-xq7v-gfw6-fj88, UBUNTU-CVE-2026-92497

## What is CVE-2026-92497?

CVE-2026-92497 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. 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: ath12k: Avoid buffer overread in ath12k_wmi_op_rx()

Currently, in ath12k_wmi_op_rx(), the firmware buffer is read without
first verifying that the buffer has enough data to hold a header. This
could result in a buffer overread.

Update the logic to verify the buffer contains at least enough data to
hold a wmi_cmd_hdr before reading from the buffer.

Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_UPSTREAM-3

## Which versions are affected by CVE-2026-92497?


## How do I fix CVE-2026-92497?

Apply the vendor's patch.

## Is CVE-2026-92497 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92497 and fix it if it is affected.

What it is: CVE-2026-92497 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. 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-2026-92497 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-2026-92497/ (Markdown: https://insights.sbomify.com/CVE-2026-92497/index.md)
```

## Sources

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

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