ksmbd: fix use-after-free in smb_lazy_parent_lease_break_close()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in smb_lazy_parent_lease_break_close()
opinfo pointer obtained via rcu_dereference(fp->f_opinfo) is being accessed after rcu_read_unlock() has been called. This creates a race condition where the memory could be freed by a concurrent writer between the unlock and the subsequent pointer dereferences (opinfo->is_lease, etc.), leading to a use-after-free.
From the CVE record · Linux
The Linux kernel's ksmbd component can access an opinfo pointer after releasing its RCU read lock. If a concurrent writer frees that memory before the pointer is dereferenced, the resulting race causes a use-after-free. 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.