CVE-2026-74279
Linux kernel cavium/cpt DMA cleanup bug causes incorrect DMA unmaps and memory corruption.
Is CVE-2026-74279 being exploited?
Not confirmed. CVE-2026-74279 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.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-74279?
CVE-2026-74279 is rated Critical with a CVSS score of 10.0. 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-74279?
Yes. A fix has been recorded for CVE-2026-74279. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74279 affect?
CVE-2026-74279 affects Linux kernel (crypto/cavium/cpt driver), Systems with Cavium/Marvell CPT crypto accelerators, Linux distributions with driver enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74279?
Apply kernel security updates immediately; restrict access to Cavium crypto devices.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can trigger incorrect DMA unmaps leading to kernel memory corruption, crashes, or potential privilege escalation on systems with Cavium CPT devices.
Immediate action required
- affected>= c694b233295b99c33dd5ac28aede9f171f5a6862 and < 23c6174e48f66fc10b998b0acdb406cb0caf5c80
- affected>= c694b233295b99c33dd5ac28aede9f171f5a6862 and < 23d3a7e896a1fe2d7a6bcb42f093948b79f8a198
- affected>= c694b233295b99c33dd5ac28aede9f171f5a6862 and < 28141f95ae93b18f9bfde953cb787fcb151fb9da
- affected>= c694b233295b99c33dd5ac28aede9f171f5a6862 and < 8afd1007ef79898a6e010eaade97097e49405fce
- affected>= c694b233295b99c33dd5ac28aede9f171f5a6862 and < 3b8a1e1f4e4071a62b20374028744e8cc8310d48
- affected>= c694b233295b99c33dd5ac28aede9f171f5a6862 and < fb4d57b83356d4bd411b45ede3024e0ff42c9b5e
- affected>= c694b233295b99c33dd5ac28aede9f171f5a6862 and < d319b83b97b3585550d9ae592dfa78c755b6129e
- affected>= c694b233295b99c33dd5ac28aede9f171f5a6862 and < 9dbf173bd32d5f81b005008b682bfb50aa093455
- affected4.11
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.