# CVE-2026-90361: wifi: ath11k: fix leak in ath11k_service_ready_ext_event()

> A memory leak in the ath11k WiFi driver allows attackers to cause denial of service by triggering error paths during TLV parsing.

- **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-102003, BELL-CVE-2026-90361, DEBIAN-CVE-2026-90361, GHSA-8gr2-cxr8-j22g, UBUNTU-CVE-2026-90361

## What is CVE-2026-90361?

CVE-2026-90361 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: ath11k: fix leak in ath11k_service_ready_ext_event()

Currently, during ath11k_service_ready_ext_event() processing,
svc_rdy_ext.mac_phy_caps can be allocated during TLV parsing. This is a
temporary allocation that is freed on the success path, but not on the
error path. If parsing succeeds far enough to allocate mac_phy_caps and
then fails on a later TLV, the allocation leaks. So free the allocation
on the error path.

Compile tested only.

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


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

Apply the vendor's patch.

## Is CVE-2026-90361 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90361 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-90361 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-90361/ (Markdown: https://insights.sbomify.com/CVE-2026-90361/index.md)
```

## Sources

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

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