Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99386

smb: client: don't resurrect an exiting tcon from cached dir workers

No exploitation reported by the sources we read.

  • Published2026-11-19
  • Fixed in7.3.2 · 6.18.61 · 6.12.117 · 6.12 · 6.7

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: don't resurrect an exiting tcon from cached dir workers cfids_laundromat_worker() bumps tcon->tc_count for every expired open cfid and queues cached_dir_offload_close() without checking whether the tcon is already being torn down. Racing with the final cifs_put_tcon(), the tcon comes back from zero and gets torn down twice: T1 T2 cifs_put_tcon() --tc_count == 0, TID_EXITING tconInfoFree() free_cached_dirs() cancel_delayed_work_sync() cfids_laundromat_worker() ++tc_count == 1 queue_work(serverclose_wq) kfree(tcon->origin_fullpath) kfree(tcon) cached_dir_offload_close() close_cached_dir() [UAF] cifs_put_tcon() tconInfoFree() [double free] cached_dir_lease_break() also bumps tc_count without tc_lock, racing with the laundromat's locked update. Take the tcon reference through a helper that refuses once the tcon is TID_EXITING or its refcount has dropped to zero. Queued put_work and close_work then always hold a tcon reference, so tconInfoFree() can't run before they finish and free_cached_dirs() doesn't need to flush any workqueue. If the laundromat can't get a reference, put the cfid back on the dying list for free_cached_dirs() to free; its handle goes away with the tree connection. The lease break path finds the tcon on ses->tcon_list under cifs_tcp_ses_lock, so it can't see TID_EXITING, but it now takes tc_lock.

Timeline

dates in UTC
  1. 2026-11-1914:23CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.27.3.2
6.x≥ 6.13.0, < 6.18.616.18.61
6.12≥ 6.12.2, < 6.12.1176.12.117
6.x≥ 6.11.11, < 6.126.12
6.x≥ 6.6.64, < 6.76.7

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 548812afd96982a76a93ba76c0582ea670c40d9e, < d1b779a4b5acf9a8692b7f002bf6d98e0597cc86fixed in d1b779a4b5acf9a8692b7f002bf6d98e0597cc86git
    • ≥ 3fa640d035e5ae526769615c35cb9ed4be6e3662, < b304a9268f7d54eb75ce62f75013c9a90eabf084fixed in b304a9268f7d54eb75ce62f75013c9a90eabf084git
    • ≥ 3fa640d035e5ae526769615c35cb9ed4be6e3662, < ed62849db326dc166aa18496e40f27a44b2c7ad0fixed in ed62849db326dc166aa18496e40f27a44b2c7ad0git
    • ≥ 3fa640d035e5ae526769615c35cb9ed4be6e3662, < d58e7b40908a8a57755811d5b37af1df3380278ffixed in d58e7b40908a8a57755811d5b37af1df3380278fgit
    • = 73934e535cffbda1490fa97d82690a0f9aa73e94no fix statedgit
    • = ff4528bbc82d0d90073751f7b49e7b9e9c7e5638no fix statedgit
    • ≥ 6.12.2, < 6.12.117fixed in 6.12.117semver
    • ≥ 6.6.64, < 6.7fixed in 6.7semver

    1 more version line in the CVE record.

  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 6.13no fix stated

    Not affected < 6.13 · ≥ 6.12.117, ≤ 6.12.* · ≥ 6.18.61, ≤ 6.18.* · ≥ 7.3.2, ≤ 7.3.* · ≥ 7.4-rc1

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-19

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • linuxDebian:14all versions · fixed in 7.3.3-1
  • linuxDebian:13all versions · fixed in 6.12.117-1
  • linux-6.12Debian:12all versions · fixed in 6.12.117-1~deb12u1
  • linux-ltsAlpaquita:streamfrom 6.18.58-r0 · fixed in 6.18.62-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed

Vendor advisories

  • CVE-2026-99386 Red Hat Product Security111 known affected

    kernel: kernel: Denial of Service via race condition in SMB client tree connection teardown

    kernel.src as a component of Red Hat Enterprise Linux 10 · bpftool as a component of Red Hat Enterprise Linux 9 · kernel as a component of Red Hat Enterprise Linux 9 · +108 more

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.2 · 6.18.61 · 6.12.117 · 6.12 · 6.7
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-99386 · 111 productsFix deferred

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2026-11-19
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-q388-r9wf-9w78

Frequently asked questions

What is CVE-2026-99386?

In the Linux kernel, the following vulnerability has been resolved: smb: client: don't resurrect an exiting tcon from cached dir workers cfids_laundromat_worker() bumps tcon->tc_count for every expired open cfid and queues cached_dir_offload_close() without checking whether the tcon is already being torn down. Racing with the final cifs_put_tcon(), the tcon comes back from zero and gets torn down twice: T1 T2 cifs_put_tcon() --tc_count == 0, TID_EXITING tconInfoFree() free_cached_dirs() cancel_delayed_work_sync() cfids_laundromat_worker() ++tc_count == 1 queue_work(serverclose_wq) kfree(tcon->origin_fullpath) kfree(tcon) cached_dir_offload_close() close_cached_dir() [UAF] cifs_put_tcon() tconInfoFree() [double free] cached_dir_lease_break() also bumps tc_count without tc_lock, racing with the laundromat's locked update. Take the tcon reference through a helper that refuses once the tcon is TID_EXITING or its refcount has dropped to zero. Queued put_work and close_work then always hold a tcon reference, so tconInfoFree() can't run before they finish and free_cached_dirs() doesn't need to flush any workqueue. If the laundromat can't get a reference, put the cfid back on the dying list for free_cached_dirs() to free; its handle goes away with the tree connection. The lease break path finds the tcon on ses->tcon_list under cifs_tcp_ses_lock, so it can't see TID_EXITING, but it now takes tc_lock.

Is CVE-2026-99386 actively exploited?

Active exploitation of CVE-2026-99386 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99386?

CVE-2026-99386 has a CVSS v3 base score of 7.5 (High severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record