Affects Linux kernel, widely used across infrastructure; could cause memory disclosure or data corruption in IPsec ESP traffic.
CVE-2026-43284
Linux kernel ESP: in-place decrypt on shared skb frags.
Is CVE-2026-43284 being exploited?
Not confirmed. CVE-2026-43284 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 93% probability of exploitation in the next 30 days.
How severe is CVE-2026-43284?
CVE-2026-43284 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-43284?
Yes. A fix has been recorded for CVE-2026-43284. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43284 affect?
CVE-2026-43284 affects Linux kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43284?
Patch promptly to fixed kernel version
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
ESP decrypts in shared memory, could leak or corrupt plaintext in IPsec ESP packets.
Patch when possible
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < a6cb440f274a22456ef3e86b457344f1678f38f9
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < ab8b995323e5237041472d07e5055f5f7dcdf15b
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < fe785bb3a8096dffcc4048a85cd0c83337eeecad
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < 5d55c7336f8032d434adcc5fab987ccc93a44aec
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < 8253aab4659ca16116b522203c2a6b18dccacea7
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < 50ed1e7873100f77abad20fd31c51029bc49cd03
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < b54edf1e9a3fd3491bdcb82a21f8d21315271e0d
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < 71a1d9d985d26716f74d21f18ee8cac821b06e97
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < 52646cbd00e765a6db9c3afe9535f26218276034
- affected>= cac2661c53f35cbe651bef9b07026a5a05ab8ce0 and < f4c50a4034e62ab75f1d5cdd191dd5f9c77fdff4
- affected4.11
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.