Answer in brief
CVE-2026-93829 records a Unknown severity vulnerability in smb: client: fix races in cifsd thread creation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ee8f811cbac56ffb738b3a73671a9e75b0f56e99 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0eee1e6cddd1d9ce14da06e0238ca8d3362dec90 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e8a5cf2ff5a13fefb228f2069e29dd7d8e37185d || >=0 <6.12.111 || >=0 <6.18.53 | ee8f811cbac56ffb738b3a73671a9e75b0f56e99, 0eee1e6cddd1d9ce14da06e0238ca8d3362dec90, e8a5cf2ff5a13fefb228f2069e29dd7d8e37185d, 6.12.111, 6.18.53 |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix races in cifsd thread creation The cifsd demultiplex thread can run and access tcp_ses before the parent thread has finished populating tcp_ses, which the worker thread accesses locklessly. Also, the kthread_run macro may start the thread before returning the thread pointer. Because the pointer is part of the structure that the thread can access, if the kernel is preempted after the thread is spawned, but before the thread pointer is populated and the thread attempts to exit, it will sleep, waiting for a SIGKILL signal. Fix this by moving creation of the thread to after all of tcp_ses'es fields are populated, and spawning the thread last, using a split kthread_create/wake_up_process logic.
Quoted source text, attributed separately from HOL analysis.