ksmbd: fix use-after-free in same_client_has_lease()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · < 0ff82a9cf9312678d8bc4edeef0b6e82659ac12a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in same_client_has_lease()
same_client_has_lease() returns an opinfo pointer from ci->m_op_list after dropping ci->m_lock without taking a reference.
smb_grant_oplock() then dereferences that pointer in copy_lease() and when checking breaking_cnt. A concurrent close can remove the old lease from ci->m_op_list and drop the last reference before the caller uses the returned pointer, leading to a use-after-free.
Take a reference when same_client_has_lease() selects an existing lease, drop any previous match while scanning, and release the returned reference in smb_grant_oplock() after copying the lease state.
From the CVE record · Linux
The Linux kernel's ksmbd lease handling can use a freed pointer when a concurrent close removes a lease before smb_grant_oplock() uses it. The input does not specify how an attacker could trigger this, whether authentication or user interaction is required, or the resulting impact.
Engineers running Linux kernels with ksmbd should check their versions against the vendor advisory; affected versions are not specified.