CVE-2026-74408
ath9k Wi‑Fi driver OOB array access can corrupt kernel memory.
Is CVE-2026-74408 being exploited?
Not confirmed. CVE-2026-74408 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-74408?
CVE-2026-74408 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-74408?
Yes. A fix has been recorded for CVE-2026-74408. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74408 affect?
CVE-2026-74408 affects Linux kernel (ath9k driver), Devices using Atheros/ath9k Wi‑Fi chips. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74408?
Update to patched kernel/driver; if delayed, disable ath9k or restrict untrusted Wi‑Fi access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Out‑of‑bounds array access from Wi‑Fi firmware can cause kernel memory corruption, enabling DoS, privilege escalation, or possible code execution via the wireless interface.
Patch when possible
- affected>= fce041beb03f93c7a771f0b4b6c45bb71ef90901 and < fb11083db9d7d6fb8f98bbba1cbfcf3fb7b4bf54
- affected>= fce041beb03f93c7a771f0b4b6c45bb71ef90901 and < 734db72d55ca578a344dfa33e30145032c074b25
- affected>= fce041beb03f93c7a771f0b4b6c45bb71ef90901 and < f5931d06b45ed402572bfe5832fff15864ef5481
- affected>= fce041beb03f93c7a771f0b4b6c45bb71ef90901 and < 46ca1451f61b598f45cb5259e066d305444d95fc
- affected>= fce041beb03f93c7a771f0b4b6c45bb71ef90901 and < a9e055ac62cb3fcea262d4b687ec73eed82b3379
- affected>= fce041beb03f93c7a771f0b4b6c45bb71ef90901 and < 5435fd3edcb11c7cc4002847c83e9a50b49284dc
- affected>= fce041beb03f93c7a771f0b4b6c45bb71ef90901 and < 336d4c8cd9b1646060ee690c881d465dfc09c6c0
- affected>= fce041beb03f93c7a771f0b4b6c45bb71ef90901 and < 7ce2f118a2389e8f0a64068c6fe7cc7d40639be0
- affected3.1
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.