# CVE-2026-98195: wifi: iwlegacy: fix broadcast stations deallocation

> A use-after-free vulnerability in the iwlegacy Wi-Fi driver allows local attackers to cause a denial of service by toggling RF kill during startup.

- **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-106170, BELL-CVE-2026-98195, DEBIAN-CVE-2026-98195, GHSA-9fj7-g454-67r4, UBUNTU-CVE-2026-98195

## What is CVE-2026-98195?

CVE-2026-98195 is an use after free 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: iwlegacy: fix broadcast stations deallocation

On the error path of __il4965_up(), il_dealloc_bcast_stations() clears
only IL_STA_UCODE_ACTIVE, leaving IL_STA_BCAST set. This causes the
same broadcast stations to be deallocated again by __il4965_down().

This can occur when RF_KILL is toggled during driver startup.

To fix clear the entire 'used' field, since we will not do any
other operations on the station.

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


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

Apply the vendor's patch.

## Is CVE-2026-98195 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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