ksmbd: fix use-after-free by using call_rcu() for oplock_info
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
d73686367ad68534257cd88a36ca3c52cb8b81d8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free by using call_rcu() for oplock_info
ksmbd currently frees oplock_info immediately using kfree(), even though it is accessed under RCU read-side critical sections in places like opinfo_get() and proc_show_files().
Since there is no RCU grace period delay between nullifying the pointer and freeing the memory, a reader can still access oplock_info structure after it has been freed. This can leads to a use-after-free especially in opinfo_get() where atomic_inc_not_zero() is called on already freed memory.
Fix this by switching to deferred freeing using call_rcu().
From the CVE record · Linux
The Linux kernel's ksmbd component frees oplock_info while readers may still access it under RCU, causing a use-after-free. This can occur when a reader accesses the structure before an RCU grace period has elapsed; the input does not specify whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with ksmbd should check their versions; affected versions are not specified.