Skip to content
major vulnerability· requires attention

Affects widely-used Linux kernel SMB client; enterprise deployments rely on SMB, enabling potential data disclosure or crash.

Systems

CVE-2026-46185

9.1
Critical
EPSS 0.51%Patch availableMay 30, 2026

Linux kernel SMB client: out-of-bounds read in symlink_data() from SMB2 error.

common questions

Is CVE-2026-46185 being exploited?

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

How severe is CVE-2026-46185?

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

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

What does CVE-2026-46185 affect?

CVE-2026-46185 affects Linux kernel SMB client (Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46185?

Patch the kernel to the fixed version immediately.

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

executive summary
technical analysis
affected
Linux kernel SMB client (Linux)
impact

Kernel memory read via crafted SMB2 error, possible data disclosure or crash.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 76894f3e2f71177747b8b4763fb180e800279585 and < 2be11faf79e49fb8250a181ff0b4d2b2f084af83
  • affected>= 76894f3e2f71177747b8b4763fb180e800279585 and < ef6495d4df6e7af8f3de67e65150881c880f696c
  • affected>= 76894f3e2f71177747b8b4763fb180e800279585 and < 15dc0a4de743a1aaa7b859b3aea79f08c695396c
  • affected>= 76894f3e2f71177747b8b4763fb180e800279585 and < b8c8a704f0bc133deb171f6aeb6f3a684203e212
  • affected>= 76894f3e2f71177747b8b4763fb180e800279585 and < b9561402489d41149f63e001a74384863b7b30a6
  • affected>= 76894f3e2f71177747b8b4763fb180e800279585 and < d62b8d236fab503c6fec1d3e9a38bea71feaca20
  • affected2d046892a493d9760c35fdaefc3017f27f91b621
  • affected>= 6.0.16 and < 6.1
  • affected6.1
vendor says fixed in< 6.1, >= 6.1.175 and <= 6.1.*, >= 6.6.140 and <= 6.6.*, >= 6.12.88 and <= 6.12.*, >= 6.18.30 and <= 6.18.*, >= 7.0.7 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