Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68312cifs: fix cifsFileInfo leak on kmalloc failure in deferred close drain paths

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e3fc065682ebbbd15b0ce0036800f4acbf765d46 – < 75143abc21f627da7ee3b0336814bd702692e830
    • affected e3fc065682ebbbd15b0ce0036800f4acbf765d46 – < c968b2417f6a15d35ff4b97d534af4a126cb510b
    • affected e3fc065682ebbbd15b0ce0036800f4acbf765d46 – < 7af7ec3af091f55d01f0ebe0246d10e37f358311
    • affected e3fc065682ebbbd15b0ce0036800f4acbf765d46 – < 6089f561e2c31a3ba52836c75c7d2ab50d2eea41
    • affected e3fc065682ebbbd15b0ce0036800f4acbf765d46 – < 32390b3f06f26e366cfb27dbac4bc0196c321535
    • affected e3fc065682ebbbd15b0ce0036800f4acbf765d46 – < c2f2e83e3bbc5483730fd4ee903182761f1ae50f
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68312 badge
[![CVE-2026-68312](https://cveledger.app/badge/CVE-2026-68312.svg)](https://cveledger.app/cve/CVE-2026-68312)

Record last updated .