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

Cc: [email protected]
Reported-by: [email protected] # ZDI-CAN-20477
Signed-off-by: Namjae Jeon <[email protected]>
Signed-off-by: Steve French <[email protected]>

diff --git a/fs/ksmbd/server.c b/fs/ksmbd/server.c
index 2ebf6985a88d68de8d626b7ee4f98f5dbe72e711..f9b2e0f19b03ba9eef9bca0ede89c2b516b70759 100644 (file)
--- a/fs/ksmbd/server.c
+++ b/fs/ksmbd/server.c
@@ -606,6 +606,7 @@ err_unregister:
 static void __exit ksmbd_server_exit(void)
 {
        ksmbd_server_shutdown();
+       rcu_barrier();
        ksmbd_release_inode_hash();
 }