Skip to main content
VulnerabilityPublished Updated

CVE-2026-31410: Linux kernel · ksmbd: use volume UUID in FS_OBJECT_ID_INFORMATION

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-31410

Not known to be exploited · CVSS 5.5 Medium · fixed in ce00616bc1df675bfdacc968f2bf7c51f4669227 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
Patch
Available – fixed in ce00616bc1df675bfdacc968f2bf7c51f4669227, c283a6ffe6d5d6e5594d991286b9ce15951572e1, 5258e9187703bfd02faf19c37c23ab9d6587f24c +3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < ce00616bc1df675bfdacc968f2bf7c51f4669227
Fixed in
  • ce00616bc1df675bfdacc968f2bf7c51f4669227
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < c283a6ffe6d5d6e5594d991286b9ce15951572e1
Fixed in
  • c283a6ffe6d5d6e5594d991286b9ce15951572e1
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 5258e9187703bfd02faf19c37c23ab9d6587f24c
Fixed in
  • 5258e9187703bfd02faf19c37c23ab9d6587f24c
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 3d80ebe6d1b7bc9ad20fd9b0c1a0c56d804f8a0a
Fixed in
  • 3d80ebe6d1b7bc9ad20fd9b0c1a0c56d804f8a0a
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 3a64125730cabc34fccfbc230c2667c2e14f7308
Fixed in
  • 3a64125730cabc34fccfbc230c2667c2e14f7308
LinuxLinuxAffected
  • ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9, < 1df0123f96f377282feaae24d8e561fff4a6541f
Fixed in
  • 1df0123f96f377282feaae24d8e561fff4a6541f

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().

References

Community reviews

Loading reviews…