Skip to content
major vulnerability· requires attention

Very high impact Linux kernel vulnerability; widely used core infrastructure, CVSS 9.1; could disrupt IT operations.

Infrastructure

CVE-2026-43083

9.1
Critical
EPSS 0.44%Patch availableMay 8, 2026

Linux kernel net ioam6 OOB access via RX queue mapping; potential kernel crash.

common questions

Is CVE-2026-43083 being exploited?

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

CVE-2026-43083 is rated Critical with a CVSS score of 9.1. 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-43083?

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

What does CVE-2026-43083 affect?

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

What should I do about CVE-2026-43083?

Update to patched kernel version 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
impact

Out-of-bounds access in RX queue mapping could crash kernel; potential privilege escalation if exploited.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= b63c5478e9cb1d1504eb02d9dac827ad24612b32 and < 6d1d9ed9b409e0662241e3d245d574a18f643494
  • affected>= b63c5478e9cb1d1504eb02d9dac827ad24612b32 and < 95a1334748c95dd15546056280ade0c4b8dd7b78
  • affected>= b63c5478e9cb1d1504eb02d9dac827ad24612b32 and < b30b1675aa2bcf0491fd3830b051df4e08a7c8ca
  • affected5.17
vendor says fixed in< 5.17, >= 6.18.24 and <= 6.18.*, >= 6.19.14 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