---
id: "CVE-2026-98700"
kind: "vulnerability"
aliases: ["CVE-2026-98700"]
title: "Linux kernel: wifi 802.3 encap frames sent on wrong band"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["infrastructure", "linux-kernel", "mac80211", "wifi"]
not_affected_if: ["no-mac80211-wifi"]
published_at: "2026-10-18T16:17:23+00:00"
first_seen_at: "2026-10-23T21:57:16+00:00"
updated_at: "2026-10-25T05:18:56+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98700", "first_seen_at": "2026-10-23T21:57:16+00:00"}]
---

# Linux kernel: wifi 802.3 encap frames sent on wrong band

In the Linux kernel's mac80211 Wi-Fi stack, frames using 802.3 encapsulation offload leave the band field unset, so the rate selection code picks rates for the wrong band. The sources describe a correctness flaw and do not state any attacker capability.

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

## How to check

- `uname -r` to see the running kernel version
- Check whether the wifi driver uses mac80211 with 802.3 encap offload enabled (unknown from the sources)

## Fix

- Update the Linux kernel to a release that includes the upstream mac80211 fix (version unknown from the sources)

## Timeline

- 2026-10-23T21:57:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98700

## From the sources

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

wifi: mac80211: set info->band for 802.3 encap offload frames

Unlike the 802.11 TX paths, ieee80211_8023_xmit() does not set
info->band from the channel context on non-MLD interfaces. It stays at
0, so ieee80211_get_tx_rates() uses the wrong band for these frames.

Set it the same way as ieee80211_build_hdr(): drop the frame if there is
no channel context, and leave the band at 0 on MLD interfaces.

---

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