CVE-2025-40039

ksmbd: Fix race condition in RPC handle list access

MEDIUM
4.7
CVSS Score
Published: October 28, 2025 at 11:48 AM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.7
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: Fix race condition in RPC handle list access The 'sess->rpc_handle_list' XArray manages RPC handles within a ksmbd session. Access to this list is intended to be protected by 'sess->rpc_lock' (an rw_semaphore). However, the locking implementation was flawed, leading to potential race conditions. In ksmbd_session_rpc_open(), the code incorrectly acquired only a read lock before calling xa_store() and xa_erase(). Since these operations modify the XArray structure, a write lock is required to ensure exclusive access and prevent data corruption from concurrent modifications. Furthermore, ksmbd_session_rpc_method() accessed the list using xa_load() without holding any lock at all. This could lead to reading inconsistent data or a potential use-after-free if an entry is concurrently removed and the pointer is dereferenced. Fix these issues by: 1. Using down_write() and up_write() in ksmbd_session_rpc_open() to ensure exclusive access during XArray modification, and ensuring the lock is correctly released on error paths. 2. Adding down_read() and up_read() in ksmbd_session_rpc_method() to safely protect the lookup.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15.145 ≤ v < 5.166.1.71 ≤ v < 6.26.13 ≤ v < 6.17.36.3 ≤ v < 6.6.1236.7 ≤ v < 6.12.531f485b54d04a920723984062c912174330a051785.15.14552b41ef2abe274f68e892aee81406f11bd1f3a6.3a4348710a7267705b75692dc1a000920481d1d92b685757c7b08d5073046fb379be965fd6c06aafc
Vendor states this is fixed in 305853cce379407090a73b38c5de5ba748893aee (fixed)
Vendor states this is fixed in 5cc679ba0f4505936124cd4179ba66bb0a4bd9f3 (fixed)
Vendor states this is fixed in 69674b029002b1d90b655f014bdf64f404efa54d (fixed)
Vendor states this is fixed in 6b615a8fb3af0baf8126cde3d4fee97d57222ffc (fixed)
Vendor states this is fixed in 6bd7e0e55dcea2cf0d391bbc21c2eb069b4be3e1 (fixed)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.53 (unaffected)
Vendor states this is fixed in 6.17.3 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.3 (unaffected)
Vendor states this is fixed in 6.6.123 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card