Skip to content
Threat Brief

← All advisories

CVE-2026-99386

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 13% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 3fa640d035e5ae526769615c35cb9ed4be6e3662 before b304a9268f7d54eb75ce62f75013c9a90eabf084b304a9268f7d54eb75ce62f75013c9a90eabf084CVE Program
LinuxLinuxfrom 3fa640d035e5ae526769615c35cb9ed4be6e3662 before ed62849db326dc166aa18496e40f27a44b2c7ad0ed62849db326dc166aa18496e40f27a44b2c7ad0CVE Program
LinuxLinuxfrom 3fa640d035e5ae526769615c35cb9ed4be6e3662 before d58e7b40908a8a57755811d5b37af1df3380278fd58e7b40908a8a57755811d5b37af1df3380278fCVE Program
LinuxLinuxfrom 548812afd96982a76a93ba76c0582ea670c40d9e before d1b779a4b5acf9a8692b7f002bf6d98e0597cc86d1b779a4b5acf9a8692b7f002bf6d98e0597cc86CVE Program
LinuxLinuxfrom 6.11.11 before 6.126.12CVE Program
LinuxLinuxfrom 6.12.2 before 6.12.1176.12.117CVE Program
LinuxLinuxfrom 6.6.64 before 6.76.7CVE Program
LinuxLinux6.13Not documentedCVE Program
LinuxLinux73934e535cffbda1490fa97d82690a0f9aa73e94Not documentedCVE Program
LinuxLinuxff4528bbc82d0d90073751f7b49e7b9e9c7e5638Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.13Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references