Skip to content
major vulnerability· requires attention

Linux kernel is pervasive; remote kernel-memory corruption (CVSS 9.8) can disrupt infrastructure and enable kernel RCE—broad impact across organizations.

Networks

CVE-2026-74662

9.8
Critical
EPSS 0.51%Patch availableAug 25, 2026

Remote kernel memory-corruption in Linux IP fragment reassembly (inet/frags).

common questions

Is CVE-2026-74662 being exploited?

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

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

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

What does CVE-2026-74662 affect?

CVE-2026-74662 affects Linux kernel (inet/frag subsystem), Linux distributions using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74662?

Apply vendor/kernel patches immediately; block or filter fragmented IP traffic.

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

executive summary
technical analysis
affected
Linux kernel (inet/frag subsystem)Linux distributions using affected kernels
impact

Remote kernel memory corruption via IP fragment reassembly; can cause DoS or enable kernel RCE/privilege escalation.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 648700f76b03b7e8149d13cc2bdb3355035258a9 and < f4e4dab62181b7fe7c011bed6fbef9fc3d48c769
  • affected>= 648700f76b03b7e8149d13cc2bdb3355035258a9 and < 4ed0681dc2c1e0538b79d2fc56190ffcb369dacd
  • affected>= 648700f76b03b7e8149d13cc2bdb3355035258a9 and < 08a04d7bfb9c103432561aff8a62b6872e694a6a
  • affected>= 648700f76b03b7e8149d13cc2bdb3355035258a9 and < d3ffb89b2944672cf7bdd8e9ee577d2043b4a956
  • affected>= 648700f76b03b7e8149d13cc2bdb3355035258a9 and < 39c6c4b267b65f00e0b0335a2ae00cbe9e3174f0
  • affected>= 648700f76b03b7e8149d13cc2bdb3355035258a9 and < 9f904dd3e455750e5d4ec9b2f134835811b85a2f
  • affected>= 648700f76b03b7e8149d13cc2bdb3355035258a9 and < 928128865e43b197e30688dc1bc991592c97edcf
  • affected>= 648700f76b03b7e8149d13cc2bdb3355035258a9 and < 653d7ddf6cba867777a3d14c4f83ace008c5ad13
  • affected493107105843f299662b3b664a83804645564f12
  • affected>= 4.4.174 and < 4.5
  • affected4.17
vendor says fixed in< 4.17, >= 5.10.267 and <= 5.10.*, >= 5.15.218 and <= 5.15.*, >= 6.1.185 and <= 6.1.*, >= 6.6.154 and <= 6.6.*, >= 6.12.106 and <= 6.12.*, >= 6.18.45 and <= 6.18.*, >= 7.1.9 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