Skip to content
Systems

CVE-2026-72329

CRITICAL
Critical
EPSS 0.18%Patch availableAug 17, 2026

Linux net/liquidio driver stale VF pci_dev deref allows host kernel crash or escalation.

common questions

Is CVE-2026-72329 being exploited?

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

How severe is CVE-2026-72329?

CVE-2026-72329 is rated Critical. 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-72329?

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

What does CVE-2026-72329 affect?

CVE-2026-72329 affects Linux kernel (net/liquidio driver), Marvell/Cavium LiquidIO SR-IOV NICs, Hosts using SR-IOV PF with OCTEON VFs, Virtualized environments with VF passthrough. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72329?

Apply vendor/kernel patch immediately; if not possible disable SR-IOV or unbind LiquidIO VFs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (net/liquidio driver)Marvell/Cavium LiquidIO SR-IOV NICsHosts using SR-IOV PF with OCTEON VFsVirtualized environments with VF passthrough
impact

A malicious SR-IOV VF mailbox request can dereference a stale VF pci_dev, causing host kernel crash (DoS) and potential privilege escalation/host compromise.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= ca6139ffc67ee6ef0459f81e37894ed411083855 and < 81acef3a247fd523513a2e9f71de1c167bc0f882
  • affected>= ca6139ffc67ee6ef0459f81e37894ed411083855 and < 5c0e3ba4f500fd4314ceb42f07f16bc445156431
  • affected4.10
vendor says fixed in< 4.10, >= 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