CVE-2026-68312: Linux kernel · cifs: fix cifsFileInfo leak on kmalloc failure in deferred close drain paths
Source GCVE Database
Not known to be exploited · fixed in c968b2417f6a15d35ff4b97d534af4a126cb510b : update Linux kernel when convenient.
Data as of 30 Oct 2026, 16:33 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in c968b2417f6a15d35ff4b97d534af4a126cb510b, c2f2e83e3bbc5483730fd4ee903182761f1ae50f, 75143abc21f627da7ee3b0336814bd702692e830 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: cifs: fix cifsFileInfo leak on kmalloc failure in deferred close drain paths In cifs_close_deferred_file(), cifs_close_all_deferred_files(), and cifs_close_deferred_file_under_dentry(), when a pending deferred close is cancelled via cancel_delayed_work(), the subsequent kmalloc_obj() to add the file to the local processing list may fail under memory pressure. The loop breaks immediately, but the cancelled work is no longer pending (it would have called _cifsFileInfo_put()), and the cfile is never added to file_head for processing. The cifsFileInfo reference and the open server handle both leak. Fix by saving the cfile that failed allocation in a local variable, breaking as before, and calling _cifsFileInfo_put() on it after releasing the lock. Any files later in the iteration are unaffected since their deferred work is still pending and will fire normally.
References
- nvd.nist.gov/vuln/detail/CVE-2026-68312 (opens in a new tab)
- git.kernel.org/stable/c/32390b3f06f26e366cfb27dbac4bc0196c321535 (opens in a new tab)
- git.kernel.org/stable/c/6089f561e2c31a3ba52836c75c7d2ab50d2eea41 (opens in a new tab)
- git.kernel.org/stable/c/75143abc21f627da7ee3b0336814bd702692e830 (opens in a new tab)
- git.kernel.org/stable/c/7af7ec3af091f55d01f0ebe0246d10e37f358311 (opens in a new tab)
- git.kernel.org/stable/c/c2f2e83e3bbc5483730fd4ee903182761f1ae50f (opens in a new tab)
- git.kernel.org/stable/c/c968b2417f6a15d35ff4b97d534af4a126cb510b (opens in a new tab)