Skip to content
major vulnerability· requires attention

Kernel networking bug affects widespread Linux deployments, enabling off‑path bypass of rate limits and UDP reconnaissance — requires org‑wide attention and patching.

Systems

CVE-2026-90110

9.4
Critical
EPSS n/aPatch availableSep 19, 2026

Linux kernel inetpeer RB-tree predictability allows off‑path rate‑limit bypass & UDP port inference

common questions

Is CVE-2026-90110 being exploited?

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

How severe is CVE-2026-90110?

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

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

What does CVE-2026-90110 affect?

CVE-2026-90110 affects Linux kernel inetpeer subsystem, Servers and appliances running affected Linux kernels, Network devices using upstream Linux kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-90110?

Apply vendor/upstream kernel updates with the inetpeer fix and reboot affected hosts.

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

executive summary
technical analysis
affected
Linux kernel inetpeer subsystemServers and appliances running affected Linux kernelsNetwork devices using upstream Linux kernel
impact

Off‑path attackers can bypass IP‑keyed ICMP/UDP rate limits and infer open UDP ports, enabling reconnaissance and potential abuse of UDP services.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= b145425f269a17ed344d737f746b844dfac60c82 and < b20e98f0bb668a59abaf7bcf85d75c073e90d352
  • affected>= b145425f269a17ed344d737f746b844dfac60c82 and < 5f127e3cc9647a8a70db12c65dbd0de473545380
  • affected>= b145425f269a17ed344d737f746b844dfac60c82 and < 199fcf285e498111e029137d088949bc6c26d578
  • affected>= b145425f269a17ed344d737f746b844dfac60c82 and < 857681f6835d5b0a7bc4a34a026baeaaf5215623
  • affected>= b145425f269a17ed344d737f746b844dfac60c82 and < 7109bb63667a53e4542ad845476f97d0c8b28a61
  • affected>= b145425f269a17ed344d737f746b844dfac60c82 and < 2ee66e9487172fcd189bc52a767c30dad7141c09
  • affected4.14
vendor says fixed in< 4.14, >= 6.1.188 and <= 6.1.*, >= 6.6.157 and <= 6.6.*, >= 6.12.110 and <= 6.12.*, >= 6.18.52 and <= 6.18.*, >= 7.2.6 and <= 7.2.*, >= 7.3-rc1 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