---
id: "CVE-2026-98916"
kind: "vulnerability"
aliases: ["CVE-2026-98916"]
title: "Linux kernel: wifi color change runs on non-beaconing link"
severity: "unknown"
cvss: null
epss: 0.00209
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["infrastructure", "kernel", "linux", "wifi"]
not_affected_if: []
published_at: "2026-10-23T12:18:25+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98916", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-98916", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# Linux kernel: wifi color change runs on non-beaconing link

The Linux kernel's nl80211 wifi interface could start a BSS color change on a link that was not beaconing, passing an invalid link to the driver. The sources do not describe a confirmed attacker outcome beyond a driver call on an invalid link.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98916
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-98916

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

wifi: nl80211: check link is beaconing for color change

When trying to do a color change, validate that the link is
beaconing first, to avoid calling the driver with an invalid
link.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_