Skip to content
Systems

CVE-2026-74411

8.8
High
EPSS 0.25%Patch availableAug 17, 2026

Linux rtw89 Wi‑Fi driver bug causes soft lockup and system panic during 6GHz scans.

common questions

Is CVE-2026-74411 being exploited?

Not confirmed. CVE-2026-74411 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.

How severe is CVE-2026-74411?

CVE-2026-74411 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-74411?

Yes. A fix has been recorded for CVE-2026-74411. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-74411 affect?

CVE-2026-74411 affects Linux kernel (rtw89 driver), Systems with Realtek rtw89 Wi‑Fi chips, Devices scanning 6GHz band. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74411?

Update Linux kernel to patched release; disable 6GHz scanning or unload rtw89 if immediate patching is impossible.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (rtw89 driver)Systems with Realtek rtw89 Wi‑Fi chipsDevices scanning 6GHz band
impact

Remote denial-of-service: crafted 6GHz Wi‑Fi activity can trigger kernel soft lockup and system panic during scanning.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= c6aa9a9c47252ac7b07ed6d10459027e2f2a2de0 and < 966fbed4b4463fbcb49c5becf3f86eae776861bd
  • affected>= c6aa9a9c47252ac7b07ed6d10459027e2f2a2de0 and < 05d46e30303275f21f13c951166d39c85df976d4
  • affected>= c6aa9a9c47252ac7b07ed6d10459027e2f2a2de0 and < 7a1ab5fdcae896e20ca6d68fa0fbd2816cb7471f
  • affected>= c6aa9a9c47252ac7b07ed6d10459027e2f2a2de0 and < 140fa699cfd0e18ab2f1497acd951fb3548610f5
  • affected>= c6aa9a9c47252ac7b07ed6d10459027e2f2a2de0 and < 08fdcb529df6df3562dd2b0035f88dd5be8b3c68
  • affected6.4
vendor says fixed in< 6.4, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free