Skip to content
Systems

CVE-2026-74285

8.8
High
EPSS 0.12%Patch availableAug 17, 2026

Linux kernel RX queue teardown bug allows device DMA to stale/zero addresses.

common questions

Is CVE-2026-74285 being exploited?

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

How severe is CVE-2026-74285?

CVE-2026-74285 is rated High with a CVSS score of 8.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-74285?

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

What does CVE-2026-74285 affect?

CVE-2026-74285 affects Linux kernel (net rxq / netkit queue lease paths), Systems running affected Linux kernels, Virtual NICs (fbnic / QEMU noted). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74285?

Install vendor kernel updates that include the RX queue teardown fix and reboot affected hosts.

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

executive summary
technical analysis
affected
Linux kernel (net rxq / netkit queue lease paths)Systems running affected Linux kernelsVirtual NICs (fbnic / QEMU noted)
impact

Device DMA to stale/zero addresses → kernel memory corruption, crashes, data corruption, possible local privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 5602ad61ebee99c83081fba1aaf5814736edc3e7 and < 03f4c6ed3cffbfce0b85a3a0193d08a46692a9f8
  • affected>= 5602ad61ebee99c83081fba1aaf5814736edc3e7 and < 37314c9dbe95b4d924c7b61aaf563cec4f4e4133
  • affected7.1
vendor says fixed in< 7.1, >= 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