Skip to content
Systems

CVE-2026-74495

9.8
Critical
EPSS 0.51%Patch availableAug 17, 2026

Linux igbvf driver off-by-one DMA cleanup bug leaks a DMA mapping, enabling kernel resource exhaustion.

common questions

Is CVE-2026-74495 being exploited?

Not confirmed. CVE-2026-74495 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-74495?

CVE-2026-74495 is rated Critical with a CVSS score of 9.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-74495?

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

What does CVE-2026-74495 affect?

CVE-2026-74495 affects Linux kernel - igbvf network driver, Hosts using Intel SR-IOV Virtual Functions (VF), Virtualized guests with igbvf passthrough. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74495?

Apply vendor/kernel update or driver backport that fixes igbvf DMA cleanup.

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

executive summary
technical analysis
affected
Linux kernel - igbvf network driverHosts using Intel SR-IOV Virtual Functions (VF)Virtualized guests with igbvf passthrough
impact

Off-by-one in TX DMA error cleanup leaks a DMA mapping per failure, enabling resource exhaustion and potential kernel DoS.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= c1fa347f20f17f14a4a1575727fa24340e8a9117 and < e42b7225c45f57b42306b80cdd3bda202bae7293
  • affected>= c1fa347f20f17f14a4a1575727fa24340e8a9117 and < e3ed89c257f6361f13df23023cd10ace830330ad
  • affected>= c1fa347f20f17f14a4a1575727fa24340e8a9117 and < 56726ff12cb6759ab90d6f5332c2377aeca7d249
  • affected>= c1fa347f20f17f14a4a1575727fa24340e8a9117 and < 31089f4eab42e0fc248ec80c26f9b0bad59ba4cc
  • affected>= c1fa347f20f17f14a4a1575727fa24340e8a9117 and < bc25d56c03e41c10bc4b40e99ca5d7b941675c04
  • affected>= c1fa347f20f17f14a4a1575727fa24340e8a9117 and < 845a9cdd9b03b7b6fa8de3ee80579780350a7f65
  • affected>= c1fa347f20f17f14a4a1575727fa24340e8a9117 and < df07003b5a6c6c9fce60d765d6a3da815a74c41c
  • affected>= c1fa347f20f17f14a4a1575727fa24340e8a9117 and < 0565052b7e2f436b7f1541f4849da96dc0aa7a0e
  • affected2.6.33
vendor says fixed in< 2.6.33, >= 5.10.265 and <= 5.10.*, >= 5.15.216 and <= 5.15.*, >= 6.1.183 and <= 6.1.*, >= 6.6.151 and <= 6.6.*, >= 6.12.103 and <= 6.12.*, >= 6.18.44 and <= 6.18.*, >= 7.1.8 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