Skip to content
major vulnerability· requires attention

Core Linux kernel vulnerability; widely used infra; potential memory corruption and privilege escalation.

Systems

CVE-2026-43341

9.8
Critical
EPSS 0.41%Patch availableMay 11, 2026

Linux kernel IOAM6 trace data overflow risks memory corruption.

common questions

Is CVE-2026-43341 being exploited?

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

How severe is CVE-2026-43341?

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

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

What does CVE-2026-43341 affect?

CVE-2026-43341 affects Linux kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43341?

Apply patched kernel version; reboot.

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

executive summary
technical analysis
affected
Linux kernel
impact

Memory corruption or kernel crash; possible local privilege escalation via crafted IOAM6 trace data.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 8c6f6fa6772696be0c047a711858084b38763728 and < d3a1fb2ca323d7a4e10ab3afbfa25e6d8921e4f2
  • affected>= 8c6f6fa6772696be0c047a711858084b38763728 and < e96d48b37708d53cbdc47f6f60b0714fc4a5f596
  • affected>= 8c6f6fa6772696be0c047a711858084b38763728 and < d1b041080086e91d3733a5438a8c51ad5d3d8e09
  • affected>= 8c6f6fa6772696be0c047a711858084b38763728 and < 77695a69baca9b99d95fad09fc78c2318736604f
  • affected>= 8c6f6fa6772696be0c047a711858084b38763728 and < 184d2e9db27c0f76226b5cad16fe29510a5d2280
  • affected>= 8c6f6fa6772696be0c047a711858084b38763728 and < d6e1c9b02d85a4f1f4ba6d68e916d9b610a3ed7d
  • affected>= 8c6f6fa6772696be0c047a711858084b38763728 and < 5e67ba9bb531e1ec6599a82a065dea9040b9ce50
  • affected5.15
vendor says fixed in< 5.15, >= 5.15.210 and <= 5.15.*, >= 6.1.168 and <= 6.1.*, >= 6.6.134 and <= 6.6.*, >= 6.12.81 and <= 6.12.*, >= 6.18.22 and <= 6.18.*, >= 6.19.12 and <= 6.19.*, >= 7.0 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