Skip to content

CVE-2026-99386 smb: client: don't resurrect an exiting tcon from cached dir workers

Unknown
Published
Updated
Exploit status
No public exploit known

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.

Affected products

ProductAffected versionsFixed in
Linux kernel >= 548812afd96982a76a93ba76c0582ea670c40d9e, < d1b779a4b5acf9a8692b7f002bf6d98e0597cc86 d1b779a4b5acf9a8692b7f002bf6d98e0597cc86
Linux kernel >= 3fa640d035e5ae526769615c35cb9ed4be6e3662, < b304a9268f7d54eb75ce62f75013c9a90eabf084 b304a9268f7d54eb75ce62f75013c9a90eabf084
Linux kernel >= 3fa640d035e5ae526769615c35cb9ed4be6e3662, < ed62849db326dc166aa18496e40f27a44b2c7ad0 ed62849db326dc166aa18496e40f27a44b2c7ad0
Linux kernel >= 3fa640d035e5ae526769615c35cb9ed4be6e3662, < d58e7b40908a8a57755811d5b37af1df3380278f d58e7b40908a8a57755811d5b37af1df3380278f
Linux kernel = 73934e535cffbda1490fa97d82690a0f9aa73e94 No fix listed
Linux kernel = ff4528bbc82d0d90073751f7b49e7b9e9c7e5638 No fix listed
Linux kernel >= 6.12.2, < 6.12.117 6.12.117
Linux kernel >= 6.6.64, < 6.7 6.7
Linux kernel >= 6.11.11, < 6.12 6.12
Linux kernel = 6.13 No fix listed
Linux kernel < 6.12.117 6.12.117
Linux kernel < 6.18.61 6.18.61
Linux kernel < 7.3.2 7.3.2
Linux kernel < 7.4-rc1 7.4-rc1

References