CVE-2025-40039ksmbd: Fix race condition in RPC handle list access
- 8.8HighCVSS base score
- 0.32%Exploitation in 30 daysEPSS · top 75% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 7 months later
· 7 months later
Published
- 9 months later
· 9 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.32% · top 75% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected a4348710a7267705b75692dc1a000920481d1d92 – < 69674b029002b1d90b655f014bdf64f404efa54d
- affected b685757c7b08d5073046fb379be965fd6c06aafc – < 6b615a8fb3af0baf8126cde3d4fee97d57222ffc
- affected b685757c7b08d5073046fb379be965fd6c06aafc – < 5cc679ba0f4505936124cd4179ba66bb0a4bd9f3
- affected b685757c7b08d5073046fb379be965fd6c06aafc – < 6bd7e0e55dcea2cf0d391bbc21c2eb069b4be3e1
- affected b685757c7b08d5073046fb379be965fd6c06aafc – < 305853cce379407090a73b38c5de5ba748893aee
- affected 1f485b54d04a920723984062c912174330a05178
- affected 052b41ef2abe274f068e892aee81406f11bd1f3a
- affected 5.15.145 – < 5.16
- affected 6.3
- unaffected < 6.3
- unaffected 6.6.123 – ≤ 6.6.*
- unaffected 6.12.53 – ≤ 6.12.*
- unaffected 6.17.3 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References5
- https://git.kernel.org/stable/c/69674b029002b1d90b655f014bdf64f404efa54d (opens in a new tab)
- https://git.kernel.org/stable/c/6b615a8fb3af0baf8126cde3d4fee97d57222ffc (opens in a new tab)
- https://git.kernel.org/stable/c/5cc679ba0f4505936124cd4179ba66bb0a4bd9f3 (opens in a new tab)
- https://git.kernel.org/stable/c/6bd7e0e55dcea2cf0d391bbc21c2eb069b4be3e1 (opens in a new tab)
- https://git.kernel.org/stable/c/305853cce379407090a73b38c5de5ba748893aee (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-36489 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-40039)Record last updated .