CVE-2026-99113

ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in

Published Oct 28, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in

smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION,
that is the whole of struct object_id_info, but writes only 46 of them:

- objid[] is 16 bytes, and when the volume UUID is not available only
sizeof(stfs.f_fsid) (8) bytes are copied into it;
- extended_info.version_string[] is STRING_LENGTH (28) bytes, and only
strlen("1.1.0") (5) bytes are copied into it.

The response buffer is zeroed on allocation (kvzalloc() in
smb2_allocate_rsp_buf()), so for a standalone request the remaining 31
bytes are zero. In a compound request they need not be. The offset of
the next response is advanced by the length pinned for the previous one,
so if a preceding command wrote its reply into the buffer and then
failed, smb2_set_err_rsp() pins only the short error response and the
next reply lands inside the area that has already been written. Only
the header is cleared there:

memset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);

The client then receives up to 31 bytes of a response it was not meant
to see, including one that failed with an access denied error.

Clear the structure before filling it in. As a side effect
version_string is now NUL terminated.

Analysis

AI-generated

Technical impact

The Linux kernel contains a flaw in the smb2_get_info_filesystem handling where the FS_OBJECT_ID_INFORMATION structure is only partially written. While the kernel zeroes the buffer on allocation, in compound SMB requests the area may be reused for subsequent replies. If a preceding command writes its reply and then fails, the buffer that follows is not fully cleared, causing the client to receive up to 31 bytes of data that it was not intended to see, including fragments of previous responses and an access denied error. This leakage can expose sensitive data from earlier SMB interactions, potentially revealing confidential information to an attacker. The primary impact is that a remote user who can send SMB compound requests to a vulnerable kernel can read portions of kernel memory that were not meant to be disclosed. The flaw arises from the system not fully initializing a buffer before transmitting it, which aligns with information disclosure weaknesses.

Affected Systems

All Linux kernel installations that have not applied the ksmbd fix are affected. No specific kernel release versions are listed in the CNA data; thus, any distribution running a non‑patched kernel is potentially vulnerable.

Risk and Exploitability

The EPSS score of < 1% indicates a low likelihood of exploitation, and the vulnerability is not listed in the CISA KEV catalog. However, the attack vector is remote, leveraging the SMB protocol to construct compound requests. The potential for information disclosure is significant because the attacker can retrieve at least 31 bytes of unintended data. The CVSS score of 4.3 indicates moderate severity, suggesting that successful exploitation could reveal sensitive data from prior SMB sessions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the patched ksmbd code that zeros the FS_OBJECT_ID_INFORMATION structure before use.
  • If a kernel upgrade cannot be performed immediately, disable or restrict the smb/cifs services (or block SMB traffic) on the affected host to prevent compound SMB requests from untrusted clients.
  • Configure network monitoring or IDS rules to detect atypical SMB compound request patterns, ensuring that any anomalous activity is logged and investigated promptly.

Generated by OpenCVE AI on October 29, 2026 at 15:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4906-1 linux security update
Ubuntu USN Ubuntu USN USN-9166-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9167-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9168-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9169-1 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-9168-2 Linux kernel (FIPS) vulnerabilities
Ubuntu USN Ubuntu USN USN-9173-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9167-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9168-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9169-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9173-2 Linux kernel vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-908
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-200
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION, that is the whole of struct object_id_info, but writes only 46 of them: - objid[] is 16 bytes, and when the volume UUID is not available only sizeof(stfs.f_fsid) (8) bytes are copied into it; - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only strlen("1.1.0") (5) bytes are copied into it. The response buffer is zeroed on allocation (kvzalloc() in smb2_allocate_rsp_buf()), so for a standalone request the remaining 31 bytes are zero. In a compound request they need not be. The offset of the next response is advanced by the length pinned for the previous one, so if a preceding command wrote its reply into the buffer and then failed, smb2_set_err_rsp() pins only the short error response and the next reply lands inside the area that has already been written. Only the header is cleared there: memset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2); The client then receives up to 31 bytes of a response it was not meant to see, including one that failed with an access denied error. Clear the structure before filling it in. As a side effect version_string is now NUL terminated.
Title ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-908

    Use of Uninitialized Resource

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:41 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 30, 2026, 1:21 PM
Severity
Moderate
Public date
Oct 28, 2026, 12:00 AM