# CVE-2026-98823: wifi: cfg80211: preserve hidden-group beacon IE ownership

> A use-after-free in the Linux kernel WiFi subsystem allows attackers to cause denial of service or execute code via crafted beacon frames.

- **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:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109386, BELL-CVE-2026-98823, DEBIAN-CVE-2026-98823, GHSA-xw2r-79g3-4r47, UBUNTU-CVE-2026-98823

## What is CVE-2026-98823?

CVE-2026-98823 is an use after free vulnerability in Linux, published on 18 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: cfg80211: preserve hidden-group beacon IE ownership

A hidden-group probe-response entry borrows its beacon IEs from the
group's beacon entry. cfg80211_update_assoc_bss_entry() can pass such
an entry to cfg80211_update_known_bss() when merging scan entries
after a channel switch.

Copying the borrowed beacon_ies into the associated entry gives the
same allocation two owners. Releasing the group's beacon entry can
then leave the associated entry pointing to freed IEs, which are
freed again when that entry is released.

Skip beacon IE replacement when the source entry belongs to a hidden
group. Preserve probe-response processing, the subsequent metadata
updates, and the existing rejection path for conflicting hidden
beacon updates.

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


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

Apply the vendor's patch.

## Is CVE-2026-98823 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98823 is an use after free vulnerability in Linux, published on 18 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-98823 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-98823/ (Markdown: https://insights.sbomify.com/CVE-2026-98823/index.md)
```

## Sources

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

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