CVE-2026-74488
Use‑after‑free in Linux mwifiex TDLS A‑MSDU parsing allows kernel memory corruption
Is CVE-2026-74488 being exploited?
Not confirmed. CVE-2026-74488 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-74488?
CVE-2026-74488 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-74488?
Yes. A fix has been recorded for CVE-2026-74488. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74488 affect?
CVE-2026-74488 affects Linux kernel (mwifiex driver), Devices using Marvell mwifiex firmware, Wi‑Fi enabled Linux systems with TDLS support. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74488?
Apply vendor/kernel security updates; block TDLS or isolate affected Wi‑Fi until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attackers can send crafted TDLS A‑MSDU frames to trigger use‑after‑free and OOB reads, causing kernel panic, info leak, or possible remote code execution.
Immediate action required
- affected>= 776f742040ca5eb6242c60f29ac73d5752a5b621 and < 707664027bb9307f7268eda403af7c4ccd9b8644
- affected>= 776f742040ca5eb6242c60f29ac73d5752a5b621 and < 3b02275833a0d3e6583627995d614fa99bdf364f
- affected>= 776f742040ca5eb6242c60f29ac73d5752a5b621 and < a1f0f7dc7eb15754e6931b433edb7beb754c996a
- affected>= 776f742040ca5eb6242c60f29ac73d5752a5b621 and < 25e5a3fe4f15e30f74eca42cbf3bcc3a3fbeda79
- affected>= 776f742040ca5eb6242c60f29ac73d5752a5b621 and < ece2ebb34247d573142617dfc534a9dc11ba59be
- affected>= 776f742040ca5eb6242c60f29ac73d5752a5b621 and < c9dcfe6b8b71369e1d732e2ff622c3696a2f032c
- affected>= 776f742040ca5eb6242c60f29ac73d5752a5b621 and < 5a21ab03829cb6d2682c127f22e2b9cd63b4393f
- affected>= 776f742040ca5eb6242c60f29ac73d5752a5b621 and < 99a948382af8a225e2d5e54a7052158cd6281cc6
- affected4.5
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.