CVE-2026-74411

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In 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)

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
Patch available.
generic

wifi: rtw89: Correct data type for scan index to avoid infinite loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/966fbed4b4463fbcb49c5becf3f86eae776861bd
generic

wifi: rtw89: Correct data type for scan index to avoid infinite loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7a1ab5fdcae896e20ca6d68fa0fbd2816cb7471f
generic

wifi: rtw89: Correct data type for scan index to avoid infinite loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/140fa699cfd0e18ab2f1497acd951fb3548610f5
generic

wifi: rtw89: Correct data type for scan index to avoid infinite loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08fdcb529df6df3562dd2b0035f88dd5be8b3c68
generic

wifi: rtw89: Correct data type for scan index to avoid infinite loop - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05d46e30303275f21f13c951166d39c85df976d4

Vendor Advisories for CVE-2026-74411(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-06ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-06ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-06ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-06ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 34× in last 7d / 131× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 228 total refreshes for this CVE.

  1. 2026-10-06 22:22 UTCEG score recompute
  2. 2026-10-06 22:22 UTCVendor advisory
  3. 2026-10-06 22:22 UTCGHSA enrichment
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-06 09:10 UTCEG score recompute
  6. 2026-10-06 09:10 UTCVendor advisory
  7. 2026-10-06 09:10 UTCGHSA enrichment
  8. 2026-10-05 17:43 UTCEPSS rescore
  9. 2026-10-05 09:41 UTCEG score recompute
  10. 2026-10-05 09:41 UTCVendor advisory
  11. 2026-10-05 09:41 UTCGHSA enrichment
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-04 21:57 UTCVendor advisory
  14. 2026-10-04 21:57 UTCGHSA enrichment
  15. 2026-10-04 06:59 UTCVendor advisory
  16. 2026-10-04 06:59 UTCGHSA enrichment
  17. 2026-10-03 19:31 UTCEG score recompute
  18. 2026-10-03 19:30 UTCVendor advisory
  19. 2026-10-03 19:30 UTCGHSA enrichment
  20. 2026-10-03 14:26 UTCEPSS rescore
  21. 2026-10-03 03:20 UTCEG score recompute
  22. 2026-10-03 03:20 UTCVendor advisory
  23. 2026-10-03 03:20 UTCGHSA enrichment
  24. 2026-10-02 15:51 UTCVendor advisory
  25. 2026-10-02 15:51 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 02:01 UTCEG score recompute
  2. 2026-10-02 02:01 UTCVendor advisory
  3. 2026-10-02 02:01 UTCGHSA enrichment
  4. 2026-10-01 19:50 UTCEPSS rescore
  5. 2026-10-01 08:28 UTCVendor advisory
  6. 2026-10-01 08:28 UTCGHSA enrichment
  7. 2026-09-30 20:58 UTCEG score recompute
  8. 2026-09-30 20:58 UTCVendor advisory
  9. 2026-09-30 20:58 UTCGHSA enrichment
  10. 2026-09-29 15:24 UTCEPSS rescore
  11. 2026-09-28 23:45 UTCEG score recompute
  12. 2026-09-28 23:45 UTCVendor advisory
  13. 2026-09-28 23:44 UTCGHSA enrichment
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 10:15 UTCVendor advisory
  16. 2026-09-28 10:15 UTCGHSA enrichment
  17. 2026-09-27 22:43 UTCEG score recompute
  18. 2026-09-27 22:43 UTCVendor advisory
  19. 2026-09-27 22:43 UTCGHSA enrichment
  20. 2026-09-27 13:48 UTCEPSS rescore
  21. 2026-09-27 08:26 UTCEG score recompute
  22. 2026-09-27 08:26 UTCVendor advisory
  23. 2026-09-27 08:26 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 00:28 UTCEPSS rescore
  26. 2026-09-25 02:31 UTCEG score recompute
  27. 2026-09-25 02:31 UTCVendor advisory
  28. 2026-09-25 02:31 UTCGHSA enrichment
  29. 2026-09-24 14:04 UTCEPSS rescore
  30. 2026-09-24 08:01 UTCVendor advisory
  31. 2026-09-24 08:01 UTCGHSA enrichment
  32. 2026-09-23 20:32 UTCEG score recompute
  33. 2026-09-23 20:32 UTCVendor advisory
  34. 2026-09-23 20:32 UTCGHSA enrichment
  35. 2026-09-23 17:54 UTCEPSS rescore
  36. 2026-09-23 08:16 UTCVendor advisory
  37. 2026-09-23 08:16 UTCGHSA enrichment
  38. 2026-09-22 20:47 UTCEG score recompute
  39. 2026-09-22 20:47 UTCVendor advisory
  40. 2026-09-22 20:47 UTCGHSA enrichment
  41. 2026-09-22 16:01 UTCEPSS rescore
  42. 2026-09-22 08:24 UTCEG score recompute
  43. 2026-09-22 08:24 UTCVendor advisory
  44. 2026-09-22 08:24 UTCGHSA enrichment
  45. 2026-09-21 21:09 UTCEPSS rescore
  46. 2026-09-21 20:55 UTCVendor advisory
  47. 2026-09-21 20:55 UTCGHSA enrichment
  48. 2026-09-21 09:25 UTCVendor advisory
  49. 2026-09-21 09:25 UTCGHSA enrichment
  50. 2026-09-20 21:57 UTCEG score recompute
  51. 2026-09-20 21:57 UTCVendor advisory
  52. 2026-09-20 21:57 UTCGHSA enrichment
  53. 2026-09-20 20:16 UTCEPSS rescore
  54. 2026-09-20 10:28 UTCVendor advisory
  55. 2026-09-20 10:28 UTCGHSA enrichment
  56. 2026-09-19 23:00 UTCEG score recompute
  57. 2026-09-19 23:00 UTCVendor advisory
  58. 2026-09-19 23:00 UTCGHSA enrichment
  59. 2026-09-19 11:02 UTCVendor advisory
  60. 2026-09-19 11:02 UTCGHSA enrichment
  61. 2026-09-18 23:19 UTCEG score recompute
  62. 2026-09-18 23:19 UTCVendor advisory
  63. 2026-09-18 23:18 UTCGHSA enrichment
  64. 2026-09-18 19:28 UTCEPSS rescore
  65. 2026-09-18 11:50 UTCVendor advisory
  66. 2026-09-18 11:50 UTCGHSA enrichment
  67. 2026-09-18 00:20 UTCEG score recompute
  68. 2026-09-18 00:20 UTCGHSA enrichment
  69. 2026-09-17 11:12 UTCGHSA enrichment
  70. 2026-09-16 23:29 UTCEG score recompute
  71. 2026-09-16 23:29 UTCGHSA enrichment
  72. 2026-09-16 14:08 UTCEPSS rescore
  73. 2026-09-16 10:21 UTCEG score recompute
  74. 2026-09-16 10:21 UTCGHSA enrichment
  75. 2026-09-16 05:15 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74411?
CVE-2026-74411 is a high vulnerability published on August 15, 2026. In 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 rtw89hwscanaddchan_ax for over 20 seconds, leading to a system…
When was CVE-2026-74411 disclosed?
CVE-2026-74411 was first published on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74411 actively exploited?
CVE-2026-74411 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74411?
CVE-2026-74411 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74411?
A fix for CVE-2026-74411 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74411 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74411

Explore →

Is Your Infrastructure Affected by CVE-2026-74411?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs