Skip to content
Systems

CVE-2026-74413

HIGH
High
EPSS 0.24%Patch availableAug 17, 2026

Type-mismatch in rtw89 PCI AER handlers causes kernel memory corruption.

common questions

Is CVE-2026-74413 being exploited?

Not confirmed. CVE-2026-74413 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.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-74413?

CVE-2026-74413 is rated High. 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-74413?

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

What does CVE-2026-74413 affect?

CVE-2026-74413 affects Linux kernel (rtw89 driver), Realtek RTL8852CE/RTL8852C and similar rtw89 Wi‑Fi chip devices, Laptops and embedded systems using those modules. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74413?

Install kernel update with rtw89 AER fix and reboot affected systems.

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)Realtek RTL8852CE/RTL8852C and similar rtw89 Wi‑Fi chip devicesLaptops and embedded systems using those modules
impact

PCI AER handler retrieves wrong pointer type leading to memory corruption, kernel panic and potential local privilege escalation via OOB reads/writes.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 16e3d93c6183649a3b210f82b83c1cb12aa5e8a3 and < aefc30e4a829c1683f6ae999df7f9310c27eae6c
  • affected>= 16e3d93c6183649a3b210f82b83c1cb12aa5e8a3 and < c1907b9a4fa9cb33d11a9af138374dd2e93f7a93
  • affected>= 16e3d93c6183649a3b210f82b83c1cb12aa5e8a3 and < 7068c379cf9aa8afe4dce4d9d82390187aa9c4d0
  • affected6.17
vendor says fixed in< 6.17, >= 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