# wifi: nl80211: clean up color-change beacon data on errors

CVE record · `CVE-2026-90346`

- **Identifiers:** `CVE-2026-90346`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 17 Sept 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 17 Sept 2026, 16:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `dc1e3cb8da8b414b37208b2fb6755fef8122504b to before 62f8c28a0fb08611e1278ab2af964550e22aac3c` (git)
  - affected: `dc1e3cb8da8b414b37208b2fb6755fef8122504b to before 5f47c9bc4a62e61f932a83680a796bc09ae48dd3` (git)
  - affected: `dc1e3cb8da8b414b37208b2fb6755fef8122504b to before bbe3a69a7b64398dddd1c989e9a40eaa57616b33` (git)
  - affected: `dc1e3cb8da8b414b37208b2fb6755fef8122504b to before 0ec1d14cf302ae7c23ec218527b2849a1fced3f4` (git)
  - affected: `dc1e3cb8da8b414b37208b2fb6755fef8122504b to before 4e0a67fbe3d9e2e1d6f81dfc607184c6b0abd3dd` (git)
  - affected: `dc1e3cb8da8b414b37208b2fb6755fef8122504b to before 927ee844c47ac2aef22c8f7a35f098ff576b398b` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.16`
  - unaffected: `before 5.16` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.57 to 6.18.*, inclusive` (semver)
  - unaffected: `7.2.6 to 7.2.*, inclusive` (semver)
  - unaffected: `7.3 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's nl80211 wireless configuration interface, in the color-change beacon handling path, can leak memory when beacon parsing fails partway through. The source does not describe how an attacker would reach this path or what impact a leak would have. The fix is in several stable kernel branches; the source lists unaffected versions from 5.16 onward on the 6.1, 6.6, 6.12 and 6.18 series, and affected versions before those, so upgrade to a fixed kernel release.

Written 12 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 11th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 17 Sept 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-90346](https://www.cve.org/CVERecord?id=CVE-2026-90346)
- [NVD: CVE-2026-90346](https://nvd.nist.gov/vuln/detail/CVE-2026-90346)

### References from the CNA

- <https://git.kernel.org/stable/c/62f8c28a0fb08611e1278ab2af964550e22aac3c>
- <https://git.kernel.org/stable/c/5f47c9bc4a62e61f932a83680a796bc09ae48dd3>
- <https://git.kernel.org/stable/c/bbe3a69a7b64398dddd1c989e9a40eaa57616b33>
- <https://git.kernel.org/stable/c/0ec1d14cf302ae7c23ec218527b2849a1fced3f4>
- <https://git.kernel.org/stable/c/4e0a67fbe3d9e2e1d6f81dfc607184c6b0abd3dd>
- <https://git.kernel.org/stable/c/927ee844c47ac2aef22c8f7a35f098ff576b398b>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-90346>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-90346/>. Everything for agents: <https://agentprime.io/llms.txt>.
