ksmbd: call rcu_barrier() in ksmbd_server_exit()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: call rcu_barrier() in ksmbd_server_exit()
racy issue is triggered the bug by racing between closing a connection and rmmod. In ksmbd, rcu_barrier() is not called at module unload time, so nothing prevents ksmbd from getting unloaded while it still has RCU callbacks pending. It leads to trigger unintended execution of kernel code locally and use to defeat protections such as Kernel Lockdown
From the CVE record · Linux
The Linux kernel's ksmbd module can unload while RCU callbacks are still pending. A local attacker can trigger unintended kernel code execution by racing a connection close with module unloading, potentially defeating protections such as Kernel Lockdown. The input does not specify whether authentication or user interaction is required.
Engineers running Linux systems with the ksmbd module should check their kernel versions; affected versions are not specified.