CVE-2026-31410
Improper Volume ID Handling in Linux ksmbd Causes Data Integrity Risk
Publication date: 2026-04-06
Last updated on: 2026-04-06
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux_kernel | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
This vulnerability relates to the Linux kernel's ksmbd component using an improper volume identifier. The fix involves using the volume UUID as the primary identifier to ensure proper volume identification.
Improper volume identification could potentially lead to issues in file system operations or security mechanisms relying on unique volume identifiers, but specific impacts are not detailed.
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's ksmbd component relates to how the volume identifier is determined. Previously, the system may not have used the proper volume UUID as the primary identifier. The fix ensures that the volume UUID (sb->s_uuid) is used as the main volume identifier. If the filesystem does not provide a UUID, it falls back to using stfs.f_fsid obtained from vfs_statfs().