Skip to main content
VulnerabilityPublished Updated

CVE-2025-40320: Linux kernel · smb: client: fix potential cfid UAF in smb2_query_info_compound

Source GCVE Database

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel. Users and administrators should apply the official kernel updates that include this patch to remediate the issue. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended mitigation. Patch status is not explicitly confirmed in the provided data; therefore, verify the vendor advisory or Linux kernel mailing lists for the exact fixed version and apply updates accordingly.

Description

A critical use-after-free vulnerability (CVE-2025-40320) was identified and resolved in the Linux kernel's SMB client code. The issue occurs in the smb2_query_info_compound() function, where a previously allocated cfid pointer may be freed during a retry attempt but not reset, leading to potential use of a stale pointer. This can cause refcount underflow and memory corruption. The fix involves reinitializing the cfid pointer to NULL during replay to prevent use-after-free.

References

Community reviews

Loading reviews…