# CVE-2026-98327: wifi: mac80211: mesh: reset the CSA state when leaving

> A memory leak in the Linux kernel's mac80211 mesh networking code allows attackers to cause a denial of service by leaving a mesh network during a channel switch.

- **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:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106248, BELL-CVE-2026-98327, DEBIAN-CVE-2026-98327, GHSA-6v32-hcc5-q9w8, UBUNTU-CVE-2026-98327

## What is CVE-2026-98327?

CVE-2026-98327 is a memory corruption vulnerability in Linux, published on 6 Oct 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: mac80211: mesh: reset the CSA state when leaving

ifmsh->csa is allocated in ieee80211_mesh_csa_beacon() and only freed
in ieee80211_mesh_finish_csa(), i.e. when the channel switch completes.
Leaving the mesh while a switch is still pending therefore leaks it.

Additionally, ifmsh->csa_role and ifmsh->chsw_ttl have their state leak
in this case, so things can get mixed up in addition to the memory
leak.

Refactor the reset and call it in ieee80211_stop_mesh() to fix it all.

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


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

Apply the vendor's patch.

## Is CVE-2026-98327 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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