CVE-2026-31410

ksmbd: use volume UUID in FS_OBJECT_ID_INFORMATION

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

ksmbd: use volume UUID in FS_OBJECT_ID_INFORMATION

Use sb->s_uuid for a proper volume identifier as the primary choice.
For filesystems that do not provide a UUID, fall back to stfs.f_fsid
obtained from vfs_statfs().

Analysis

AI-generated

Technical impact

The reported issue in the Linux kernel concerns the ksmbd SMB service’s handling of volume identifiers when responding to FS_OBJECT_ID_INFORMATION requests. The code originally relied on an incorrect source of volume data, and the new commit changes the logic to use the filesystem’s UUID (sb->s_uuid) as the primary identifier, falling back to the filesystem ID obtained from vfs_statfs() when a UUID is unavailable. This change is intended to correct the misuse of structure data that could result in malformed or duplicated volume identifiers being returned to SMB clients.

Affected Systems

Administrators should note that all Linux kernels before the patch are affected. The fix is incorporated in the mainline kernel following commit 3a641257..., and applies to all releases that ship the kernel, including versions 7.0 RC1–RC4 and later stable releases. Anyone running a kernel that lacks the updated ksmbd logic is potentially exposed to the incorrect volume identifier behavior. Checking the kernel version and ensuring it includes the relevant commit is necessary for remediation.

Risk and Exploitability

The CVSS score assigned to this vulnerability is 5.5, reflecting a moderate impact. The EPSS score is less than 1 %, indicating a low probability that attackers will target this weakness. It is not listed in the CISA KEV catalog, and no public exploits have been reported. An attacker would need the ability to interact with the ksmbd service over SMB to provoke the flaw, which generally requires network or local access. Consequently, the risk is considered low to moderate, mainly concerning potential confusion or misidentification of shares rather than direct compromise.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that contains the ksmbd volume UUID fix
  • Limit SMB traffic to known, trusted hosts by configuring firewall rules or network segmentation
  • Monitor SMB share listings for unexpected duplicate or incorrect identifiers to detect configuration issues

Generated by OpenCVE AI on May 20, 2026 at 18:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4906-1 linux security update
Debian DSA Debian DSA DSA-6238-1 linux security update
Ubuntu USN Ubuntu USN USN-9173-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9175-1 Linux kernel (Oracle) vulnerabilities
Ubuntu USN Ubuntu USN USN-9173-2 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9183-1 Linux kernel (FIPS) vulnerabilities
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
Metrics cvssV3_1

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

Type Values Removed Values Added
Weaknesses CWE-318
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ksmbd: use volume UUID in FS_OBJECT_ID_INFORMATION Use sb->s_uuid for a proper volume identifier as the primary choice. For filesystems that do not provide a UUID, fall back to stfs.f_fsid obtained from vfs_statfs().
Title ksmbd: use volume UUID in FS_OBJECT_ID_INFORMATION
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:24 PM
Reserved
Mar 9, 2026, 3:48 PM
Status
Modified
Published
Apr 6, 2026, 8:16 AM
Modified
Oct 30, 2026, 1:18 PM
Severity
Public date
Apr 6, 2026, 12:00 AM