GHSA-V332-427P-Q486
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: reset ar->num_stations on hardware start
When (multiple) hw restart occurs, we end up in a situation where we cannot accept new stations / mesh peers. This seems to be the 'num_stations' in 'struct ath11k' that did not get reset properly in this case. In ath11k_mac_op_start(), it was indeed the only accounting var that did not get reset so let's clear it too.
This avoids problems like those:
[1248828.088023] WARNING: CPU: 0 PID: 12281 at net/mac80211/util.c:1682 ieee80211_reconfig_stations+0x98/0xc0
[1248828.088115] Call trace:
[1248828.088116] ieee80211_reconfig_stations+0x98/0xc0 (P)
[1248828.088119] ieee80211_reconfig+0x774/0x1438
[1248828.088123] ieee80211_restart_work+0x10c/0x178
[1248828.088127] process_one_work+0x178/0x3c0
[1248828.088130] worker_thread+0x280/0x440
[1248828.088133] kthread+0xe0/0xf8
[1248828.088137] ret_from_fork+0x10/0x20
[1248828.088141] ---[ end trace 0000000000000000 ]---
[1248836.686604] ath11k_pci 0000:04:00.0: refusing to associate station: too many connected already (128)
[1248836.686609] ath11k_pci 0000:04:00.0: Failed to add station: xx:xx:xx:xx:xx:xx for VDEV: 1
Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1
{
"affected": [],
"aliases": [
"CVE-2026-98936"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:14Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath11k: reset ar-\u003enum_stations on hardware start\n\nWhen (multiple) hw restart occurs, we end up in a situation where we\ncannot accept new stations / mesh peers. This seems to be the\n\u0027num_stations\u0027 in \u0027struct ath11k\u0027 that did not get reset properly in\nthis case. In ath11k_mac_op_start(), it was indeed the only accounting var\nthat did not get reset so let\u0027s clear it too.\n\nThis avoids problems like those:\n\n\t[1248828.088023] WARNING: CPU: 0 PID: 12281 at net/mac80211/util.c:1682 ieee80211_reconfig_stations+0x98/0xc0\n\t[1248828.088115] Call trace:\n\t[1248828.088116] ieee80211_reconfig_stations+0x98/0xc0 (P)\n\t[1248828.088119] ieee80211_reconfig+0x774/0x1438\n\t[1248828.088123] ieee80211_restart_work+0x10c/0x178\n\t[1248828.088127] process_one_work+0x178/0x3c0\n\t[1248828.088130] worker_thread+0x280/0x440\n\t[1248828.088133] kthread+0xe0/0xf8\n\t[1248828.088137] ret_from_fork+0x10/0x20\n\t[1248828.088141] ---[ end trace 0000000000000000 ]---\n\t[1248836.686604] ath11k_pci 0000:04:00.0: refusing to associate station: too many connected already (128)\n\t[1248836.686609] ath11k_pci 0000:04:00.0: Failed to add station: xx:xx:xx:xx:xx:xx for VDEV: 1\n\nTested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1",
"id": "GHSA-v332-427p-q486",
"modified": "2026-10-23T15:31:31Z",
"published": "2026-10-23T15:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98936"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/60142eb2afda34508e640a3ff2a54c90e51525cc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7e0ad05ebc72fffba2bdf2400400902d94ed7272"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9a9467f7cc633b31e4c34a2c56aa095e0c3fa853"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c27779d3679c695674747744390f97a5424a0dc8"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c3ac51701e925e8d50479ae2fddca51a09f636e8"
}
],
"schema_version": "1.4.0",
"severity": []
}
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
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.