PT-2026-151567

CVE-2026-99386

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾