# wifi: ath12k: fix memory leak in ath12k_pci_remove()

CVE record · `CVE-2025-37744`

- **Identifiers:** `CVE-2025-37744`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2025, 12:55 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `fc38e9339c47d704934bc74e55c331f0d2d88583 to before 52e3132e62c31b5ade43dc4495fa81175e6e8398` (git)
  - affected: `fc38e9339c47d704934bc74e55c331f0d2d88583 to before 1b24394ed5c8a8d8f7b9e3aa9044c31495d46f2e` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.14`
  - unaffected: `before 6.14` (semver)
  - unaffected: `6.14.3 to 6.14.*, inclusive` (semver)
  - unaffected: `6.15 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's ath12k wifi driver leaks firmware memory on PCI device removal. In ath12k_pci_remove(), firmware memory allocated during probe was not freed when the ATH12K_FLAG_QMI_FAIL bit was set. The affected range is given as commits rather than version numbers, with 6.14 listed as affected and 6.14.3 and later, plus 6.15 and later, as unaffected. The source gives few details on exploitability, and no workaround is listed. The fix is to free the memory via ath12k_fw_unmap(), so upgrade to a kernel version that includes it.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 5th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2025, 12:55 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-37744)
- 1 May 2025, 13:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-37744)

## Sources

- [CVE List: CVE-2025-37744](https://www.cve.org/CVERecord?id=CVE-2025-37744)
- [NVD: CVE-2025-37744](https://nvd.nist.gov/vuln/detail/CVE-2025-37744)

### References from the CNA

- <https://git.kernel.org/stable/c/52e3132e62c31b5ade43dc4495fa81175e6e8398>
- <https://git.kernel.org/stable/c/1b24394ed5c8a8d8f7b9e3aa9044c31495d46f2e>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-37744>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-37744/>. Everything for agents: <https://agentprime.io/llms.txt>.
