Linux kernel is ubiquitous; a kernel-level sk_msg accounting flaw risks widespread disruption (DoS or RCE) across servers, appliances, and endpoints.
CVE-2026-72041
Linux kernel espintcp sk_msg accounting bug may allow kernel memory corruption.
Is CVE-2026-72041 being exploited?
Not confirmed. CVE-2026-72041 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.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-72041?
CVE-2026-72041 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-72041?
Yes. A fix has been recorded for CVE-2026-72041. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72041 affect?
CVE-2026-72041 affects Linux kernel (espintcp / TCP network stack). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72041?
Apply latest Linux kernel security updates and reboot affected hosts immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted TCP packets can corrupt kernel sk_msg state, causing crashes (DoS) and potential privilege escalation or remote code execution.
Immediate action required
- affected>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 518dcb84b997dff461800b079e5f2596389f766a
- affected>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 4ea8c051b4bd7feec7749a980f2f70e1782b84d7
- affected>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < a977f78adce40b39d90d9567e7987bb110102810
- affected>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 54d73f18f8919735f4d04d6f43374f75756c0180
- affected>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 14c0b42c8a2cd9b5361bbff45b52f69c62c6a286
- affected>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < a66d45e0ce6d73cd79962d422388e61bfaf0cb50
- affected>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < a338ce41bc933d8f74c39d9b3b6f1d8ca53d9714
- affected>= e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 007800408002d871f5699bdb944f985896730b8f
- 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.