GHSA-75CW-HG5P-HXFV
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In the Linux kernel, the following vulnerability has been resolved:
wifi: rtw89: Correct data type for scan index to avoid infinite loop
A kernel soft lockup was observed during Wi-Fi scanning on the 6GHz band. The CPU becomes stuck in rtw89_hw_scan_add_chan_ax for over 20 seconds, leading to a system panic.
RIP points to 0f b6 c3 (movzbl %bl, %eax), which zero-extends the low 8 bits of RBX into RAX. RBX (the counter i) has reached a huge value: 0x137466a1.
watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kworker/u16:4:6124] Workqueue: events_unbound cfg80211_wiphy_work [cfg80211] RIP: 0010:rtw89_hw_scan_add_chan_ax+0xb3/0x6e0 [rtw89_core] Code: a0 48 89 45 a8 44 89 6d 9c 44 89 75 98 eb 29 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 83 c3 01 <0f> b6 c3 41 3b 44 24 74 0f 83 0b 02 00 00 0f b6 c3 48 8d 14 80 49 RSP: 0018:ffffcb48cbaa39f8 EFLAGS: 00000202 RAX: 0000000000000005 RBX: 00000000137466a1 RCX: 0000000000000000 RDX: ffff89ffc9d851a8 RSI: 0000000000004f0d RDI: 0000000096af0130 RBP: ffffcb48cbaa3a60 R08: 0000000000000000 R09: ffff8a00b7502080 R10: ffff8a00b75ff600 R11: 0000000000000000 R12: ffff89ffc7553870 R13: ffff8a00b7ac8f19 R14: ffff8a00b75020d8 R15: ffff89ffc3d54d80 FS: 0000000000000000(0000) GS:ffff8a014f962000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007558d7f9f4c4 CR3: 0000000178040001 CR4: 00000000001706f0 Call Trace: rtw89_hw_scan_prep_chan_list_ax+0x8a/0x400 [rtw89_core] rtw89_hw_scan_start+0x546/0x8a0 [rtw89_core] ? rtw89_fw_h2c_default_cmac_tbl+0x13c/0x1f0 [rtw89_core] rtw89_ops_hw_scan+0xae/0x120 [rtw89_core] drv_hw_scan+0xbb/0x180 [mac80211] __ieee80211_start_scan+0x2fc/0x750 [mac80211] ieee80211_request_scan+0xe/0x20 [mac80211] ieee80211_scan+0x123/0x190 [mac80211] rdev_scan+0x40/0x110 [cfg80211] cfg80211_scan_6ghz+0x5a1/0xa30 [cfg80211]
By objdump with source:
for (i = 0; i < req->n_6ghz_params; i++) {
5fbc0: 83 c3 01 add $0x1,%ebx --> i++ 5fbc3: 0f b6 c3 movzbl %bl,%eax --> get counter fbc6: 41 3b 44 24 74 cmp 0x74(%r12),%eax
- RBX: 00000000137466a1 -> %bl = a1 -> EAX = 000000a1 (161)
{
"affected": [],
"aliases": [
"CVE-2026-74411"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:43Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw89: Correct data type for scan index to avoid infinite loop\n\nA kernel soft lockup was observed during Wi-Fi scanning on the 6GHz band.\nThe CPU becomes stuck in rtw89_hw_scan_add_chan_ax for over 20 seconds,\nleading to a system panic.\n\nRIP points to 0f b6 c3 (movzbl %bl, %eax), which zero-extends\nthe low 8 bits of RBX into RAX.\nRBX (the counter i) has reached a huge value: 0x137466a1.\n\n watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kworker/u16:4:6124]\n Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]\n RIP: 0010:rtw89_hw_scan_add_chan_ax+0xb3/0x6e0 [rtw89_core]\n Code: a0 48 89 45 a8 44 89 6d 9c 44 89 75 98 eb 29 66 66 2e 0f 1f\n 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 83 c3 01\n \u003c0f\u003e b6 c3 41 3b 44 24 74 0f 83 0b 02 00 00 0f b6 c3 48 8d 14 80 49\n RSP: 0018:ffffcb48cbaa39f8 EFLAGS: 00000202\n RAX: 0000000000000005 RBX: 00000000137466a1 RCX: 0000000000000000\n RDX: ffff89ffc9d851a8 RSI: 0000000000004f0d RDI: 0000000096af0130\n RBP: ffffcb48cbaa3a60 R08: 0000000000000000 R09: ffff8a00b7502080\n R10: ffff8a00b75ff600 R11: 0000000000000000 R12: ffff89ffc7553870\n R13: ffff8a00b7ac8f19 R14: ffff8a00b75020d8 R15: ffff89ffc3d54d80\n FS: 0000000000000000(0000) GS:ffff8a014f962000(0000)\n knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007558d7f9f4c4 CR3: 0000000178040001 CR4: 00000000001706f0\n Call Trace:\n \u003cTASK\u003e\n rtw89_hw_scan_prep_chan_list_ax+0x8a/0x400 [rtw89_core]\n rtw89_hw_scan_start+0x546/0x8a0 [rtw89_core]\n ? rtw89_fw_h2c_default_cmac_tbl+0x13c/0x1f0 [rtw89_core]\n rtw89_ops_hw_scan+0xae/0x120 [rtw89_core]\n drv_hw_scan+0xbb/0x180 [mac80211]\n __ieee80211_start_scan+0x2fc/0x750 [mac80211]\n ieee80211_request_scan+0xe/0x20 [mac80211]\n ieee80211_scan+0x123/0x190 [mac80211]\n rdev_scan+0x40/0x110 [cfg80211]\n cfg80211_scan_6ghz+0x5a1/0xa30 [cfg80211]\n\nBy objdump with source:\n\n\tfor (i = 0; i \u003c req-\u003en_6ghz_params; i++) {\n 5fbc0:\t83 c3 01 \tadd $0x1,%ebx --\u003e i++\n 5fbc3:\t0f b6 c3 \tmovzbl %bl,%eax --\u003e get counter\n fbc6:\t41 3b 44 24 74 \tcmp 0x74(%r12),%eax\n\n * RBX: 00000000137466a1 -\u003e %bl = a1 -\u003e EAX = 000000a1 (161)",
"id": "GHSA-75cw-hg5p-hxfv",
"modified": "2026-08-17T06:33:44Z",
"published": "2026-08-15T06:32:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74411"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/05d46e30303275f21f13c951166d39c85df976d4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/08fdcb529df6df3562dd2b0035f88dd5be8b3c68"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/140fa699cfd0e18ab2f1497acd951fb3548610f5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7a1ab5fdcae896e20ca6d68fa0fbd2816cb7471f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/966fbed4b4463fbcb49c5becf3f86eae776861bd"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.
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.