CVE-2026-23226
Use-After-Free in Linux ksmbd_chann_list Causes Memory Corruption
Publication date: 2026-02-18
Last updated on: 2026-04-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.3 (inc) to 6.18.11 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's ksmbd component, specifically involving the ksmbd_chann_list xarray. The issue is that this xarray lacks proper synchronization, which can lead to a use-after-free condition during multi-channel sessions. This happens between the functions lookup_chann_list() and ksmbd_chann_del. The vulnerability was addressed by adding a read-write semaphore called chann_lock to the ksmbd_session structure, which protects all accesses to the xarray such as loading, storing, and erasing entries.
How can this vulnerability impact me? :
The vulnerability allows a use-after-free condition in multi-channel sessions within the ksmbd component of the Linux kernel. This could potentially lead to memory corruption, crashes, or unexpected behavior in the kernel, which might be exploited to cause denial of service or possibly escalate privileges depending on the context of use.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know