Skip to main content
VulnerabilityPublished Updated

CVE-2025-38431: Linux kernel · smb: client: fix regression with native SMB symlinks

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-38431· Low

Not known to be exploited · CVSS 5.5 Low : upgrade to ff8abbd248c1f52df0c321690b88454b13ff54b2 or 6ddaf7567080c7de2e0c99efca2ee1e6b79beea5 when convenient.

Data as of 13 Nov 2026, 18:29 UTC

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

Thin evidence

One scorer or none
Patch
Available – fixed in ff8abbd248c1f52df0c321690b88454b13ff54b2, 6ddaf7567080c7de2e0c99efca2ee1e6b79beea5
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 25 Jul 2025

  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 13 Nov 2026.

What to do

Upgrade Linux kernel to ff8abbd248c1f52df0c321690b88454b13ff54b2 or 6ddaf7567080c7de2e0c99efca2ee1e6b79beea5.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 12b466eb52d926802b6898d2cb7e67386467f54a, < ff8abbd248c1f52df0c321690b88454b13ff54b2
Fixed in
  • ff8abbd248c1f52df0c321690b88454b13ff54b2
LinuxLinuxAffected
  • ≥ 12b466eb52d926802b6898d2cb7e67386467f54a, < 6ddaf7567080c7de2e0c99efca2ee1e6b79beea5
Fixed in
  • 6ddaf7567080c7de2e0c99efca2ee1e6b79beea5
LinuxLinuxAffected
  • =6.14
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix regression with native SMB symlinks Some users and customers reported that their backup/copy tools started to fail when the directory being copied contained symlink targets that the client couldn't parse - even when those symlinks weren't followed. Fix this by allowing lstat(2) and readlink(2) to succeed even when the client can't resolve the symlink target, restoring old behavior.

References

Community reviews

Loading reviews…