---
id: CVE-2026-93829
title: |-
  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…
summary: |-
  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…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    ee8f811cbac56ffb738b3a73671a9e75b0f56e99
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    0eee1e6cddd1d9ce14da06e0238ca8d3362dec90
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    e8a5cf2ff5a13fefb228f2069e29dd7d8e37185d
  - Linux < 6.12.111
  - Linux < 6.18.53
  - Linux (all versions)
published: '2026-09-24'
updated: '2026-09-24'
sourceUpdated: '2026-09-24T17:17:16.630'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-93829'
references:
  - url: 'https://git.kernel.org/stable/c/0eee1e6cddd1d9ce14da06e0238ca8d3362dec90'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e8a5cf2ff5a13fefb228f2069e29dd7d8e37185d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ee8f811cbac56ffb738b3a73671a9e75b0f56e99'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-24T16:47:15.889Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
