# CVE-2025-37943: wifi: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi

> A memory corruption vulnerability in the Linux kernel ath12k Wi-Fi driver allows attackers to cause invalid data access, potentially leading to code execution or system crashes.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 20 May 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-37943, DEBIAN-CVE-2025-37943, GHSA-38h5-7v7x-v6pw, RHSA-2025:9068, ROOT-OS-UBUNTU-2204-CVE-2025-37943, ROOT-OS-UBUNTU-2404-CVE-2025-37943, UBUNTU-CVE-2025-37943

## What is CVE-2025-37943?

CVE-2025-37943 is a high-severity memory corruption vulnerability in Linux kernel, published on 20 May 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: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi

In certain cases, hardware might provide packets with a
length greater than the maximum native Wi-Fi header length.
This can lead to accessing and modifying fields in the header
within the ath12k_dp_rx_h_undecap_nwifi function for
DP_RX_DECAP_TYPE_NATIVE_WIFI decap type and
potentially resulting in invalid data access and memory corruption.

Add a sanity check before processing the SKB to prevent invalid
data access in the undecap native Wi-Fi function for the
DP_RX_DECAP_TYPE_NATIVE_WIFI decap type.

Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-37943?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kpatch-patch-5_14_0-570_17_1` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_6 |
| `kpatch-patch-5_14_0-570_17_1-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_6 |
| `kpatch-patch-5_14_0-570_17_1-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1-1.el9_6 |

Products: Linux kernel.

## How do I fix CVE-2025-37943?

Apply the vendor's patch.

## Is CVE-2025-37943 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-37943 and fix it if it is affected.

What it is: CVE-2025-37943 is a high-severity memory corruption vulnerability in Linux kernel, published on 20 May 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-2025-37943 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2025-37943/ (Markdown: https://insights.sbomify.com/CVE-2025-37943/index.md)
```

## Sources

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

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