Skip to content
major vulnerability· requires attention

Affects the Linux kernel (widely deployed); high-severity race can corrupt kernel memory and potentially enable kernel compromise or broad DoS across Linux hosts.

Systems

CVE-2026-90235

9.8
Critical
EPSS n/aPatch availableSep 19, 2026

Linux kernel sunrpc race may cause kernel memory corruption, potential kernel compromise or DoS.

common questions

Is CVE-2026-90235 being exploited?

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

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

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

What does CVE-2026-90235 affect?

CVE-2026-90235 affects Linux kernel (sunrpc/xprtsock), Systems using AF_LOCAL/UDP/TCP sockets, Many Linux distributions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-90235?

Apply vendor/stable kernel updates or upstream patch immediately.

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

executive summary
technical analysis
affected
Linux kernel (sunrpc/xprtsock)Systems using AF_LOCAL/UDP/TCP socketsMany Linux distributions
impact

Race condition in sunrpc xprtsock can invoke stale kernel callbacks via AF_LOCAL/UDP/TCP sockets, causing kernel memory corruption, possible DoS or remote/local kernel code execution.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= a246b0105bbd9a70a698f69baae2042996f2a0e9 and < ed80d009b154aa204f541d390884851b3d4f15ae
  • affected>= a246b0105bbd9a70a698f69baae2042996f2a0e9 and < 589f761236e05ff9de1bdfd6a5258f113e6457fe
  • affected>= a246b0105bbd9a70a698f69baae2042996f2a0e9 and < da652cb17f9faeea1fa44b7215e8869a0b10b664
  • affected>= a246b0105bbd9a70a698f69baae2042996f2a0e9 and < d8f0b83753809761a560c4b33249388548ba6e43
  • affected>= a246b0105bbd9a70a698f69baae2042996f2a0e9 and < 33930840b5f0a79f826e7c69dc6cd78f72a67481
  • affected2.6.15
vendor says fixed in< 2.6.15, >= 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