CVE-2026-74492
Linux netfilter ipset bug allows kernel memory corruption and crashes via packet-side adds.
Is CVE-2026-74492 being exploited?
Not confirmed. CVE-2026-74492 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-74492?
CVE-2026-74492 is rated High. 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-74492?
Yes. A fix has been recorded for CVE-2026-74492. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74492 affect?
CVE-2026-74492 affects Linux kernel with netfilter/ipset enabled, Systems using iptables/nftables with ipset. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74492?
Apply vendor Linux kernel updates for ipset immediately and reboot as required.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel memory corruption from ipset packet-side adds leading to crashes (DoS) and potential local privilege escalation or arbitrary kernel compromise.
Patch when possible
- affected>= f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 6f13f4d52d06986c18f12e8bffaab944dd27ceab
- affected>= f66ee0410b1c3481ee75e5db9b34547b4d582465 and < f9d6cabff1fca010562dcdb0d22b296bdca3ba5a
- affected>= f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 16bfa7be2d76ca1e0aacfa363482e1bf8ab5042a
- affected>= f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 661ff9c0cfbe07f8eed920dde9f7781491738207
- affected>= f66ee0410b1c3481ee75e5db9b34547b4d582465 and < c710e9bf38e4e71a8db85d26a0f70c0674664207
- affected>= f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 4ae701848e4ba9e9713375fb7d82218cbd309da2
- affected>= f66ee0410b1c3481ee75e5db9b34547b4d582465 and < 77dbb248a5cc7a5270cd37bbb0b635bf059a872a
- affected>= f66ee0410b1c3481ee75e5db9b34547b4d582465 and < f30415929be8aeb002d557c8d3f7ab2d2188003a
- affected5dd9488ae41070b69d2f4acb580f77db5705f9ca
- affecteda469bab3386aebff33c59506f3a95e35b91118fd
- affected>= 5.4.24 and < 5.5
- affected>= 5.5.8 and < 5.6
- affected5.6
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.