CVE-2026-99578 (GCVE-0-2026-99578)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 8da3a71216a0ecd02980dff5cf9739376249fc72
(git)
Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < aa383c35d3e3688da8da0993f751c7b4bab66b02 (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 781af5ab5a848b3c0767c0f057bd6692e3b7c17e (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < c710c7c2e0380d7c0eeb33b686262edcaef7cb07 (git) Affected: 0 , < 6.12.118 (semver) Affected: 0 , < 6.18.64 (semver) Affected: 0 , < 7.3.5 (semver) |
guessed | |
| Linux | Linux |
Unaffected:
6.12.118 , ≤ 6.12.*
(semver)
Unaffected: 6.18.64 , ≤ 6.18.* (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/realtek/rtw88/usb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "8da3a71216a0ecd02980dff5cf9739376249fc72",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "aa383c35d3e3688da8da0993f751c7b4bab66b02",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "781af5ab5a848b3c0767c0f057bd6692e3b7c17e",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "c710c7c2e0380d7c0eeb33b686262edcaef7cb07",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "6.12.118",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "6.18.64",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "7.3.5",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/realtek/rtw88/usb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.118",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.64",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw88: usb: route bmc frames via the high queue only for DTIM delivery\n\nIn AP mode every broadcast and multicast data frame is routed to\nTX_DESC_QSEL_HIGH, the after-DTIM queue, whether or not anybody is\nasleep. The firmware drains that queue at beacon pace, a dozen or so\nframes per second measured on RTL8822BU, while one associated client\u0027s\nmDNS/SSDP chatter alone exceeds that. The excess accumulates inside\nthe chip until the shared TX page pool is exhausted (measured: 14 of\n1803 pages left). From that point every host-sourced frame queues\nbehind the backlog: authentication responses reach the air seconds\nafter the client has given up, so no station can associate anymore,\nand the beacon reserved-page download fails the BCN_VALID poll\n(\"error beacon valid\") because it needs pages from the same pool. The\nAP keeps beaconing, so the failure looks like a silent RX stall and\nonly a reboot recovers.\n\nmac80211 already decides when after-DTIM delivery is needed: it sets\nIEEE80211_TX_CTL_SEND_AFTER_DTIM on bmc frames only while at least one\nstation is actually dozing. Honor that instead of routing\nunconditionally: flagged frames keep going through the high queue with\nthe MORE_DATA and HGQMD handling introduced by commit 076f786a0ae1\n(\"wifi: rtw88: Fix AP mode incorrect DTIM behavior\"), everything else\nleaves at line rate through the AC queues. This partially reverts the\nusb.c hunk of that commit, whose unconditional routing is what lets\nthe backlog build up.\n\nOn a bench AP (USB2, 20 MHz, WPA2, hostapd, a Windows client driven\nthrough disconnect/reconnect cycles): reconnects fail 0/5 on RTL8822BU\nand 0/3 on RTL8821CU before this change, and pass 10/10 and 5/5 with\nit, with the page pool staying healthy and no beacon errors logged."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:49:10.728Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/8da3a71216a0ecd02980dff5cf9739376249fc72"
},
{
"url": "https://git.kernel.org/stable/c/aa383c35d3e3688da8da0993f751c7b4bab66b02"
},
{
"url": "https://git.kernel.org/stable/c/781af5ab5a848b3c0767c0f057bd6692e3b7c17e"
},
{
"url": "https://git.kernel.org/stable/c/c710c7c2e0380d7c0eeb33b686262edcaef7cb07"
}
],
"title": "wifi: rtw88: usb: route bmc frames via the high queue only for DTIM delivery",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99578",
"datePublished": "2026-11-20T05:49:10.728Z",
"dateReserved": "2026-09-25T10:25:14.423Z",
"dateUpdated": "2026-11-20T05:49:10.728Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/realtek/rtw88/usb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "8da3a71216a0ecd02980dff5cf9739376249fc72",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "aa383c35d3e3688da8da0993f751c7b4bab66b02",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "781af5ab5a848b3c0767c0f057bd6692e3b7c17e",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "c710c7c2e0380d7c0eeb33b686262edcaef7cb07",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "6.12.118",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "6.18.64",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"lessThan": "7.3.5",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/realtek/rtw88/usb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw88: usb: route bmc frames via the high queue only for DTIM delivery\n\nIn AP mode every broadcast and multicast data frame is routed to\nTX_DESC_QSEL_HIGH, the after-DTIM queue, whether or not anybody is\nasleep. The firmware drains that queue at beacon pace, a dozen or so\nframes per second measured on RTL8822BU, while one associated client\u0027s\nmDNS/SSDP chatter alone exceeds that. The excess accumulates inside\nthe chip until the shared TX page pool is exhausted (measured: 14 of\n1803 pages left). From that point every host-sourced frame queues\nbehind the backlog: authentication responses reach the air seconds\nafter the client has given up, so no station can associate anymore,\nand the beacon reserved-page download fails the BCN_VALID poll\n(\"error beacon valid\") because it needs pages from the same pool. The\nAP keeps beaconing, so the failure looks like a silent RX stall and\nonly a reboot recovers.\n\nmac80211 already decides when after-DTIM delivery is needed: it sets\nIEEE80211_TX_CTL_SEND_AFTER_DTIM on bmc frames only while at least one\nstation is actually dozing. Honor that instead of routing\nunconditionally: flagged frames keep going through the high queue with\nthe MORE_DATA and HGQMD handling introduced by commit 076f786a0ae1\n(\"wifi: rtw88: Fix AP mode incorrect DTIM behavior\"), everything else\nleaves at line rate through the AC queues. This partially reverts the\nusb.c hunk of that commit, whose unconditional routing is what lets\nthe backlog build up.\n\nOn a bench AP (USB2, 20 MHz, WPA2, hostapd, a Windows client driven\nthrough disconnect/reconnect cycles): reconnects fail 0/5 on RTL8822BU\nand 0/3 on RTL8821CU before this change, and pass 10/10 and 5/5 with\nit, with the page pool staying healthy and no beacon errors logged."
}
],
"id": "CVE-2026-99578",
"lastModified": "2026-11-20T06:17:48.980",
"metrics": {},
"published": "2026-11-20T06:17:48.980",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/781af5ab5a848b3c0767c0f057bd6692e3b7c17e"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8da3a71216a0ecd02980dff5cf9739376249fc72"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/aa383c35d3e3688da8da0993f751c7b4bab66b02"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c710c7c2e0380d7c0eeb33b686262edcaef7cb07"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T10:20:00+00:00",
"cve": "CVE-2026-99578",
"id": "CVE-2026-99578",
"initial_release_date": "2026-11-20T05:49:10.728000+00:00",
"product_status:known_affected": "113",
"product_status:known_not_affected": "91",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of Service in rtw88 driver via broadcast frame queue exhaustion",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99578.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.