CVE-2023-32246
BaseFortify
Publication date: 2025-08-16
Last updated on: 2025-11-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's ksmbd module where a race condition happens between closing a connection and unloading the module (rmmod). The module does not call rcu_barrier() during unload, which means it can be unloaded while there are still pending RCU callbacks. This can lead to unintended execution of kernel code locally and can be used to bypass protections like Kernel Lockdown.
How can this vulnerability impact me? :
The vulnerability can allow an attacker with local access to trigger unintended execution of kernel code, potentially defeating kernel security protections such as Kernel Lockdown. This could lead to privilege escalation or other unauthorized actions on the affected system.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that the ksmbd kernel module is updated to a version where rcu_barrier() is properly called during module unload. Avoid unloading the ksmbd module while connections are active to prevent race conditions. Applying the latest Linux kernel updates that include the fix is recommended.