# CVE-2026-99578: wifi: rtw88: usb: route bmc frames via the high queue only for DTIM delivery

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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

wifi: rtw88: usb: route bmc frames via the high queue only for DTIM delivery

In AP mode every broadcast and multicast data frame is routed to
TX_DESC_QSEL_HIGH, the after-DTIM queue, whether or not anybody is
asleep. The firmware drains that queue at beacon pace, a dozen or so
frames per second measured on RTL8822BU, while one associated client's
mDNS/SSDP chatter alone exceeds that. The excess accumulates inside
the chip until the shared TX page pool is exhausted (measured: 14 of
1803 pages left). From that point every host-sourced frame queues
behind the backlog: authentication responses reach the air seconds
after the client has given up, so no station can associate anymore,
and the beacon reserved-page download fails the BCN_VALID poll
("error beacon valid") because it needs pages from the same pool. The
AP keeps beaconing, so the failure looks like a silent RX stall and
only a reboot recovers.

mac80211 already decides when after-DTIM delivery is needed: it sets
IEEE80211_TX_CTL_SEND_AFTER_DTIM on bmc frames only while at least one
station is actually dozing. Honor that instead of routing
unconditionally: flagged frames keep going through the high queue with
the MORE_DATA and HGQMD handling introduced by commit 076f786a0ae1
("wifi: rtw88: Fix AP mode incorrect DTIM behavior"), everything else
leaves at line rate through the AC queues. This partially reverts the
usb.c hunk of that commit, whose unconditional routing is what lets
the backlog build up.

On a bench AP (USB2, 20 MHz, WPA2, hostapd, a Windows client driven
through disconnect/reconnect cycles): reconnects fail 0/5 on RTL8822BU
and 0/3 on RTL8821CU before this change, and pass 10/10 and 5/5 with
it, with the page pool staying healthy and no beacon errors logged.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 076f786a0ae14a81f40314b96a2d815e264bc213; < 8da3a71216a0ecd02980dff5cf9739376249fc72 (affected, git); ≥ 076f786a0ae14a81f40314b96a2d815e264bc213; < aa383c35d3e3688da8da0993f751c7b4bab66b02 (affected, git); ≥ 076f786a0ae14a81f40314b96a2d815e264bc213; < 781af5ab5a848b3c0767c0f057bd6692e3b7c17e (affected, git); ≥ 076f786a0ae14a81f40314b96a2d815e264bc213; < c710c7c2e0380d7c0eeb33b686262edcaef7cb07 (affected, git). Source: CNA: Linux
- Linux / Linux: 6.5 (affected); ≥ 0; < 6.5 (unaffected, semver); ≥ 6.12.118; ≤ 6.12.* (unaffected, semver); ≥ 6.18.64; ≤ 6.18.* (unaffected, semver); ≥ 7.3.5; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.20% as of 2026-11-21; percentile 10.10%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/8da3a71216a0ecd02980dff5cf9739376249fc72 (CNA: Linux)

- https://git.kernel.org/stable/c/aa383c35d3e3688da8da0993f751c7b4bab66b02 (CNA: Linux)

- https://git.kernel.org/stable/c/781af5ab5a848b3c0767c0f057bd6692e3b7c17e (CNA: Linux)

- https://git.kernel.org/stable/c/c710c7c2e0380d7c0eeb33b686262edcaef7cb07 (CNA: Linux)

- https://git.kernel.org/stable/c/781af5ab5a848b3c0767c0f057bd6692e3b7c17e (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/8da3a71216a0ecd02980dff5cf9739376249fc72 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/aa383c35d3e3688da8da0993f751c7b4bab66b02 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/c710c7c2e0380d7c0eeb33b686262edcaef7cb07 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99578; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99578; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99578; retrieved 2026-11-22; source updated Not reported

Revision: c02987ee0c45b425adc448b78744043d206fc320fb6848cacf1fc93081eacf8e

Canonical: https://y2.dev/cve/CVE-2026-99578

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.