Description
In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION

smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION,
that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns
FileSysIdentifier. Those eight bytes go to the client as they are found
in the response buffer.

The buffer is zeroed on allocation, so a standalone request leaks
nothing. A compound request can leak: the offset of the next response
is advanced by the length pinned for the previous one, so a reply that
was written into the buffer and then dropped in favour of the short
error response of smb2_set_err_rsp() stays there, and the next reply is
laid over it with only the header cleared.

Report the file system id statfs() returned, which is what the field is
for. FileSysIdentifier is __le64 and f_fsid is a pair of ints, so
assemble the value first, val[0] as the low half, and convert it on the
way out.
Published: 2026-10-28
Score: n/a
EPSS: n/a
KEV: No
Impact: Information Disclosure
Action: Apply Patch
AI Analysis

Impact

The ksmbd service in the Linux kernel does not correctly populate the FileSysIdentifier field in the FS_POSIX_INFORMATION structure during SMB2 filesystem information queries. The eight‑byte field, which should carry the file system serial number obtained from statfs(), is left empty. When a client sends compound SMB2 requests, the response buffer can retain data from a previous reply; the empty field is then overwritten with leftover bytes, causing the kernel to transmit the server’s file system identifier to the client. This results in an information‑disclosure flaw that reveals low‑level system identifiers but does not provide any direct code execution or privilege escalation capability. The flaw is a classic example of CWE‑200: Information Exposure through Protocol Leak.

Affected Systems

All Linux kernel builds that include the ksmbd component are potentially vulnerable, regardless of the kernel version, since the CVE data does not specify a limited range. The issue is confined to kernel images compiled with ksmbd enabled and with SMB2 support; users running a default distribution kernel with ksmbd active may therefore be exposed.

Risk and Exploitability

The public scanner metrics are missing a CVSS score and EPSS estimate, and the vulnerability is not listed in CISA’s KEV catalog, indicating a moderate publicly known risk. The likely attack vector is a network‑based attacker who can reach the SMB port and send crafted SMB2 compound requests. Exploitation requires only the ability to issue SMB commands; no authentication or privilege is required on the client side. Once triggered, the impact is limited to disclosure of the file system serial number, which may aid in reconnaissance or fingerprinting but does not directly compromise the system.

Generated by OpenCVE AI on October 28, 2026 at 13:08 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that incorporates the ksmbd fix from the Linux kernel STABLE series
  • If an immediate update is unavailable, disable the ksmbd module or compile the kernel without ksmbd support
  • Restrict SMB access by firewall rules to trusted IP ranges or by requiring authentication before allowing SMB2 compound requests
  • Monitor SMB traffic for unusual compound request patterns and block suspicious connections

Generated by OpenCVE AI on October 28, 2026 at 13:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 28 Oct 2026 13:45:00 +0000

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux

Wed, 28 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200

Wed, 28 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier. Those eight bytes go to the client as they are found in the response buffer. The buffer is zeroed on allocation, so a standalone request leaks nothing. A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared. Report the file system id statfs() returned, which is what the field is for. FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.
Title ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-28T10:34:32.347Z

Reserved: 2026-09-25T10:25:14.392Z

Link: CVE-2026-99115

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-28T11:17:31.023

Modified: 2026-10-28T11:17:31.023

Link: CVE-2026-99115

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-28T13:30:20Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor