# smb: client: fix regression with native SMB symlinks

CVE record · `CVE-2025-38431`

- **Identifiers:** `CVE-2025-38431`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 25 Jul 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 25 Jul 2025, 14:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `12b466eb52d926802b6898d2cb7e67386467f54a to before 6ddaf7567080c7de2e0c99efca2ee1e6b79beea5` (git)
  - affected: `12b466eb52d926802b6898d2cb7e67386467f54a to before ff8abbd248c1f52df0c321690b88454b13ff54b2` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.14`
  - unaffected: `before 6.14` (semver)
  - unaffected: `6.15.5 to 6.15.*, inclusive` (semver)
  - unaffected: `6.16 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel SMB client is affected in version 6.14; earlier versions are unaffected. The source gives few details on attacker requirements or impact. It describes backup and copy tools failing when a directory contains symlinks the client cannot parse, even when those symlinks are not followed. Upgrade to Linux 6.15.5 or 6.16 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 5th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 25 Jul 2025, 14:22 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-38431)
- 25 Jul 2025, 15:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-38431)

## Sources

- [CVE List: CVE-2025-38431](https://www.cve.org/CVERecord?id=CVE-2025-38431)
- [NVD: CVE-2025-38431](https://nvd.nist.gov/vuln/detail/CVE-2025-38431)

### References from the CNA

- <https://git.kernel.org/stable/c/6ddaf7567080c7de2e0c99efca2ee1e6b79beea5>
- <https://git.kernel.org/stable/c/ff8abbd248c1f52df0c321690b88454b13ff54b2>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-38431>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-38431/>. Everything for agents: <https://agentprime.io/llms.txt>.
