CVE-2026-74280
Linux kernel Marvell OcteonTX crypto DMA cleanup bug leading to kernel memory corruption/DoS.
Is CVE-2026-74280 being exploited?
Not confirmed. CVE-2026-74280 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.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-74280?
CVE-2026-74280 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-74280?
Yes. A fix has been recorded for CVE-2026-74280. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74280 affect?
CVE-2026-74280 affects Linux kernel (marvell/octeontx crypto driver), Devices using Marvell OcteonTX SoCs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74280?
Install kernel update containing the Marvell/octeontx fix and reboot affected hosts; restrict access to the device interface.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel memory corruption and repeated/unmapped DMA entries causing crashes (DoS) and potential local privilege escalation via malformed DMA/device operations.
Patch when possible
- affected>= 10b4f09491bfeb0b298cb2f49df585510ee6189a and < 97f150ba3e372256eabb93bd80c2cf3740077fb5
- affected>= 10b4f09491bfeb0b298cb2f49df585510ee6189a and < 8a0db9fad3c97e6447a92417cb95d7c55eaa9530
- affected>= 10b4f09491bfeb0b298cb2f49df585510ee6189a and < 8d301e5a51173ba56ce4f632a2a33bf6b14b0fcf
- affected>= 10b4f09491bfeb0b298cb2f49df585510ee6189a and < ed374dbc70c10c4a864414b3d9c257faec8fd485
- affected>= 10b4f09491bfeb0b298cb2f49df585510ee6189a and < 6c721a3e43344f8560ee4ef506fc1f72b4646dcd
- affected>= 10b4f09491bfeb0b298cb2f49df585510ee6189a and < 5f99a396f706afc749448659d1565991330e4f71
- affected>= 10b4f09491bfeb0b298cb2f49df585510ee6189a and < acff30cfc0d72465b51b0bfdf019f1cb54e15314
- affected>= 10b4f09491bfeb0b298cb2f49df585510ee6189a and < 7891c64c0520519782470ba29bac8a5761e295d8
- affected5.7
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.