Skip to content
major vulnerability· requires attention

High-severity kernel flaw in ksmbd with potential remote memory corruption; affects Linux widely.

Systems

CVE-2026-31705

9.8
Critical
EPSS 0.39%Patch availableMay 3, 2026

Linux ksmbd OOB write in smb2_get_ea() can corrupt kernel memory.

common questions

Is CVE-2026-31705 being exploited?

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

How severe is CVE-2026-31705?

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

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

What does CVE-2026-31705 affect?

CVE-2026-31705 affects Linux kernel with ksmbd (SMB server). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-31705?

Apply kernel update promptly; reboot to apply

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

executive summary
technical analysis
affected
Linux kernel with ksmbd (SMB server)
impact

Remote kernel memory corruption via OOB write in ksmbd SMB2 EA handling; could allow privilege escalation or system crash.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 9f297df20d93411c0b4ddad7f88ba04a7cd36e77 and < ddbbc8b2a09dd2cfed90871313e3691ae1db08a2
  • affected>= e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d and < ffbce350c6fd1e99116ea57383b9031717e36d3b
  • affected>= e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d and < 98f3de6ef4efbd899348d333f0902dc4ff14380c
  • affected>= e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d and < 790304c02bf9bd7b8171feda4294d6e62d32ae8f
  • affected>= e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d and < 922d48fe8c19f388ffa2f709f33acaae4e408de2
  • affected>= e2b76ab8b5c9327ab2dae6da05d0752eb2f4771d and < 30010c952077a1c89ecdd71fc4d574c75a8f5617
  • affectedf2283680a80571ca82d710bc6ecd8f8beac67d63
  • affected>= 6.1.71 and < 6.1.175
  • affected>= 5.15.145 and < 5.16
  • affected6.6
vendor says fixed in< 6.6, >= 6.1.175 and <= 6.1.*, >= 6.6.136 and <= 6.6.*, >= 6.12.84 and <= 6.12.*, >= 6.18.25 and <= 6.18.*, >= 7.0.2 and <= 7.0.*, >= 7.1 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