Skip to content
major vulnerability· requires attention

Core OS infrastructure; Linux kernel is widely deployed and a netfilter memory-read risk could disrupt networks.

Networks

CVE-2026-43452

8.2
High
EPSS 0.44%Patch availableMay 11, 2026

Linux kernel netfilter option walkers unsafe tail-read; fixed by added bounds check.

common questions

Is CVE-2026-43452 being exploited?

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

How severe is CVE-2026-43452?

CVE-2026-43452 is rated High with a CVSS score of 8.2. 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-43452?

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

What does CVE-2026-43452 affect?

CVE-2026-43452 affects Linux kernel (netfilter xt_tcpudp, xt_dccp). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-43452?

Update to patched kernel and reboot

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

executive summary
technical analysis
affected
Linux kernel (netfilter xt_tcpudp, xt_dccp)
impact

Potential kernel memory read via crafted netfilter options; may cause information disclosure or kernel crash.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 2e4e6a17af35be359cc8f1c924f8f198fbd478cc and < c2a445367a496a3c25dbc940c10c8bd1cfd4c14a
  • affected>= 2e4e6a17af35be359cc8f1c924f8f198fbd478cc and < ae1e1267650638136b84c23f2b31250f0ccb6823
  • affected>= 2e4e6a17af35be359cc8f1c924f8f198fbd478cc and < c39f84e4be1be63fc60ca7141ea7b76edcea5907
  • affected>= 2e4e6a17af35be359cc8f1c924f8f198fbd478cc and < 9b94f0e42ed248eb31929da84ed9f5310d7ff540
  • affected>= 2e4e6a17af35be359cc8f1c924f8f198fbd478cc and < 5b18b8b35c7cded2d17b2b2604c9b0694ff48d1c
  • affected>= 2e4e6a17af35be359cc8f1c924f8f198fbd478cc and < bc18551c6169eac5ed813778d3e3e484002dbbe5
  • affected>= 2e4e6a17af35be359cc8f1c924f8f198fbd478cc and < d04800323336eebf441d153f43234eac9b833d36
  • affected>= 2e4e6a17af35be359cc8f1c924f8f198fbd478cc and < cfe770220ac2dbd3e104c6b45094037455da81d4
  • affected2.6.16
vendor says fixed in< 2.6.16, >= 5.10.253 and <= 5.10.*, >= 5.15.203 and <= 5.15.*, >= 6.1.167 and <= 6.1.*, >= 6.6.130 and <= 6.6.*, >= 6.12.78 and <= 6.12.*, >= 6.18.19 and <= 6.18.*, >= 6.19.9 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