ksmbd: safely discard unregistered deferred locks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · < 054bcca4cd9f00719b01f7108b51a2168fb94f15| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: safely discard unregistered deferred locks
When vfs_lock_file() defers a lock, smb2_lock() puts its ksmbd_lock on rollback_list before allocating and registering the asynchronous work. If either operation fails, rollback assumes that smb_lock->conn is initialized and dereferences NULL. The deferred file_lock also remains linked into the VFS blocked-lock state while it is freed.
Keep the lock off rollback_list until async setup succeeds. On setup failures, explicitly unblock and wake the deferred lock before freeing it and its ksmbd wrapper.
From the CVE record · Linux
In Linux kernel ksmbd, a deferred lock can be freed while still linked to the VFS blocked-lock state if asynchronous setup fails. The rollback path can also dereference a NULL pointer, potentially crashing the kernel. The input does not specify authentication or user-interaction requirements.
Operators running Linux kernels with ksmbd should check their kernel vendor’s advisory; affected versions are not specified.