Linux KSMBD hit by two CVSS 9.0 RCE flaws, with no mainline fix yet

Linux KSMBD hit by two CVSS 9.0 RCE flaws, with no mainline fix yet

N
News Editor
2026-10-22 18:05:31
Two remote code execution flaws affecting KSMBD, the in-kernel SMB server for Linux, have been disclosed with CVSS scores of 9.0. The issues, tracked as ZDI-CAN-33549 and ZDI-CAN-33774, were posted by Trend Micro’s Zero Day Initiative to the public Linux kernel mailing list, a move that drew criticism from stable kernel maintainer Greg Kroah-Hartman. One of the flaws, ZDI-CAN-33774, can be triggered before authentication, according to the public summaries cited in the source material. As of early Oct. 23 Taipei time, no named fixes had appeared in either mainline or linux-next, and no CVE IDs had been assigned. The exposure is not universal across Linux systems: the risk is centered on machines that have compiled and enabled KSMBD, which is marked experimental and disabled by default. The source notes that such deployments are more likely in self-built NAS setups and some enterprise file-sharing nodes, while Red Hat documentation says RHEL kernels do not ship with ksmbd. Administrators are advised to verify whether the module is loaded, disable it if not needed, and restrict network exposure if SMB service must remain online while patches work their way downstream.

Two remote code execution vulnerabilities in KSMBD, the Linux kernel’s built-in SMB server module, have been disclosed with CVSS scores of 9.0. One of them, ZDI-CAN-33774, can be triggered before authentication. As of early Oct. 23 Taipei time, no formal fix had appeared in either mainline or linux-next, and no CVE IDs had been assigned.

According to Phoronix, Trend Micro’s Zero Day Initiative sent several vulnerability reports to the public Linux Kernel Mailing List rather than the usual private security list. Stable kernel maintainer Greg Kroah-Hartman then questioned that disclosure process.

Two KSMBD bugs are at the center of the disclosure

The two issues tied directly to KSMBD are ZDI-CAN-33549 and ZDI-CAN-33774, both rated 9.0 on the CVSS scale. A roundup by The Hacker News said that, as of around early Oct. 23 Taipei time, neither had a named fix in mainline or linux-next. The source also notes that the Linux project typically assigns CVEs only after a fix has landed in the stable tree.

ZDI credited the findings to TrendAI. The source says Linux kernel security documentation updated in May 2026 states that flaws found by AI tools are considered public by definition and should be sent to subsystem developer lists. In this case, ZDI also copied the public list and did not include a patch, which triggered pushback from maintainers.

What KSMBD is, and which systems are exposed

Linux kernel documentation describes KSMBD as an SMB3 file-sharing server implemented in kernel space. Performance-sensitive operations such as open, read, and write run in the kernel, while account handling and some management functions are handled by the user-space ksmbd-tools package. The configuration option is marked experimental and is disabled by default.

That means the exposed surface is not every Linux machine. The systems at risk are those that have both compiled and enabled KSMBD. The source says those deployments are more commonly found in self-built NAS systems and some enterprise file-sharing nodes, not across all Linux hosts. It also cites Red Hat documentation saying RHEL kernels do not include ksmbd and that past related CVEs stated Red Hat products were not affected.

Administrators can check whether the module is loaded with lsmod | grep ksmbd or systemctl status ksmbd, and can also verify whether CONFIG_SMB_SERVER is enabled in the kernel configuration.

One flaw is pre-auth, the other requires SMB Direct

ZDI-CAN-33774 is described as a protocol handler race condition. Based on public summaries from The Hacker News and ZDI, a sequence of short SMB1 packets followed immediately by SMB2 packets may cause a worker thread to parse a shorter SMB1 buffer with an SMB2 handler, leading to an out-of-bounds read. After share access is obtained, the path may also reach an out-of-bounds write. The issue is described as triggerable before network authentication, covering hosts that expose port 445 to the network and have KSMBD enabled.

ZDI-CAN-33549 is an integer underflow in the SMB Direct path. An attacker would need an RDMA-capable interface, whether hardware-based or through the rxe software driver, along with a writable KSMBD share and successful SMB Direct negotiation. The conditions are narrower, but the issue is still classified at the remote code execution level.

Patch status: still not in mainline

Phoronix said a fix for ZDI-CAN-33549 already exists in a Git branch expected to be merged into Linux v7.5, which could speed its path into mainline.

Even after a fix reaches mainline, it usually takes several weeks before it flows into stable or LTS kernels shipped by Linux distributions. During that window, if a host must continue offering SMB service, the source says administrators can reduce exposure by using firewall rules to restrict port 445 and SMB Direct-related ports, and by disabling guest-accessible shares.

Mitigation steps focus on disabling or isolating KSMBD

The most direct response is to disable KSMBD: unload the module, block it from loading with a modprobe blacklist, and use user-space Samba instead when an in-kernel SMB server is not required. The source says Red Hat’s mitigation guidance for earlier ksmbd issues also included creating a blacklist entry under /etc/modprobe.d/, rebuilding initramfs, and rebooting.

If file sharing must remain enabled for business reasons, the source recommends limiting source networks, disabling unnecessary SMB1 and guest access, and turning off unused SMB Direct. Operators running NAS systems or self-compiled kernels are named as the first group that should inventory exposure, while desktop distributions that have not enabled the module face lower risk.

The key point in the source is not that all Linux systems are affected. The risk sits with nodes that have KSMBD enabled and are serving traffic externally, at a time when technical details are public but patches and CVE identifiers are still not fully in place. Administrators are advised to verify module status, isolate exposed systems at the network level, and track distribution security updates rather than waiting for a CVE number to appear.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
10100

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.

Linux KSMBD hit by two CVSS 9.0 RCE flaws, with no mainline fix yet | Bit.Fan