Back
CVE-2026-31410ksmbd: use volume UUID in FS_OBJECT_ID_INFORMATION
- 5.5MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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().
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 5258e9187703bfd02faf19c37c23ab9d6587f24c
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 1df0123f96f377282feaae24d8e561fff4a6541f
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < ce00616bc1df675bfdacc968f2bf7c51f4669227
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 3d80ebe6d1b7bc9ad20fd9b0c1a0c56d804f8a0a
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < c283a6ffe6d5d6e5594d991286b9ce15951572e1
- affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 3a64125730cabc34fccfbc230c2667c2e14f7308
- affected 5.15
- unaffected < 5.15
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.78 – ≤ 6.12.*
- unaffected 6.18.20 – ≤ 6.18.*
- unaffected 6.19.10 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/5258e9187703bfd02faf19c37c23ab9d6587f24c (opens in a new tab)
- https://git.kernel.org/stable/c/1df0123f96f377282feaae24d8e561fff4a6541f (opens in a new tab)
- https://git.kernel.org/stable/c/ce00616bc1df675bfdacc968f2bf7c51f4669227 (opens in a new tab)
- https://git.kernel.org/stable/c/3d80ebe6d1b7bc9ad20fd9b0c1a0c56d804f8a0a (opens in a new tab)
- https://git.kernel.org/stable/c/c283a6ffe6d5d6e5594d991286b9ce15951572e1 (opens in a new tab)
- https://git.kernel.org/stable/c/3a64125730cabc34fccfbc230c2667c2e14f7308 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-19194 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31410)Record last updated .