Skip to content
Systems

CVE-2026-74309

10.0
Critical
EPSS 0.44%Patch availableAug 17, 2026

Linux kernel vdpa/octeon_ep IRQ mapping bug may allow kernel crash or exploitation

common questions

Is CVE-2026-74309 being exploited?

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

How severe is CVE-2026-74309?

CVE-2026-74309 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-74309?

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

What does CVE-2026-74309 affect?

CVE-2026-74309 affects Linux kernel (vdpa/octeon_ep driver), Marvell Octeon vDPA endpoint devices, Virtualization hosts using vDPA-enabled NICs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74309?

Apply vendor/kernel security update 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 (vdpa/octeon_ep driver)Marvell Octeon vDPA endpoint devicesVirtualization hosts using vDPA-enabled NICs
impact

Incorrect IRQ-to-ring mapping can cause kernel panic (DoS), packet corruption, and may enable privilege escalation or code execution on affected hosts.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 26f8ce06af6475b33b0bc60261e9f5027f9af58f and < 3ef0cfa77a3d526591be069850d186c255e3f0cc
  • affected>= 26f8ce06af6475b33b0bc60261e9f5027f9af58f and < c6c7eae5de798442987619434171ac886035d57c
  • affected>= 26f8ce06af6475b33b0bc60261e9f5027f9af58f and < 0d21a1d6375a05274291e32c1ab7cd57dbb69513
  • affected6.14
vendor says fixed in< 6.14, >= 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