External risk intelligence

Linux Kernel ksmbd Alternate Data Stream Credentials Bypass

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-64391

The vulnerability exists in ksmbd, a kernel-based SMB server. While SMB is typically used within internal networks for file sharing, it is sometimes exposed to the internet in misconfigured or specific enterprise deployments. Because the protocol is not intended for public-facing use but can be reachable if improperly configured, it fits the definition of possible exposure.

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This critical vulnerability in the Linux kernel's file-sharing component could allow unauthorized access and modification of data. The issue lies in how credentials are handled during specific file operations, potentially exposing sensitive information. While the affected component is typically used internally, misconfigurations could lead to external exposure, necessitating a review of system access controls and network configurations.

  • Handles file access credentials improperly.
  • Matters for securing internal data sharing.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted network requests to a system running a vulnerable Linux kernel. This could allow them to bypass permission checks when accessing alternate data streams, potentially leading to unauthorized data access or modification.

  • Network access required.
  • Triggered by accessing alternate data streams.
  • Risk of unauthorized data access or modification.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, this vulnerability in the Linux kernel's ksmbd could allow for unauthorized access to or modification of alternate data streams (ADS) associated with files. This occurs because ADS are treated as extended attributes (xattrs) and their I/O operations might not correctly recheck permissions, potentially using the credentials from when the SMB handle was opened instead of the current task's credentials.

  • File system metadata could be at risk.
  • Incorrect permission checks may allow exposure.
  • Unauthorized data access or modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Linux kernel's ksmbd component, which handles SMB file sharing, likely falls under the purview of infrastructure or platform teams responsible for the kernel and its associated services. The first practical step is to identify all instances of the affected ksmbd service, determine its network reachability, and assess business criticality. This will help pinpoint the accountable owner and inform a risk-based remediation plan, which may involve coordination with vendor management if a specific distribution or product is impacted.

  • Identify affected infrastructure owners.
  • Verify ksmbd network exposure.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the ksmbd component in the Linux kernel?

ksmbd is an in-kernel server that allows Linux systems to share files and printers over a network using the SMB protocol. It is primarily used to provide high-performance file sharing capabilities within enterprise environments, allowing Windows and Linux clients to access shared storage resources seamlessly.

How does CVE-2026-64391 impact credential handling?

This vulnerability involves an improper permission check. When accessing Alternate Data Streams—files stored as extended attributes—the kernel previously failed to re-verify permissions against the current user's credentials. Instead, it relied on the credentials captured when the SMB handle was first opened, which may no longer be appropriate or secure for the specific file I/O operation.

Do I need to access Alternate Data Streams to trigger this bug?

Yes. The vulnerability specifically affects the read and write paths of Alternate Data Streams, which are handled differently than standard file I/O because they interact with extended attributes. Simply accessing regular file contents or performing standard directory operations does not trigger this specific credential bypass flaw.

How do I know if my systems are relevant based on Halo Surface Signal?

According to Halo Surface Signal, this issue is relevant if you run ksmbd, which is usually found on internal networks. However, because some enterprise deployments misconfigure SMB, it can become reachable from the internet. You should determine if your ksmbd service is exposed beyond your internal network, as that significantly increases the potential risk from this vulnerability.

When should I start addressing CVE-2026-64391?

You should begin by identifying all servers running the ksmbd service. Once identified, map their network reachability to see if they are accessible from untrusted zones. Coordinate with your platform or infrastructure teams to review system access controls and prepare to apply vendor-provided kernel updates as they become available for your specific Linux distribution.

References