filelock: Remove locks reliably when fcntl/close race is detected
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c293621bbf678a3d85e3ed721c3921c8a670610d · < 5f5d0799eb0a01d550c21b7894e26b2d9db55763| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
filelock: Remove locks reliably when fcntl/close race is detected
When fcntl_setlk() races with close(), it removes the created lock with do_lock_file_wait(). However, LSMs can allow the first do_lock_file_wait() that created the lock while denying the second do_lock_file_wait() that tries to remove the lock. Separately, posix_lock_file() could also fail to remove a lock due to GFP_KERNEL allocation failure (when splitting a range in the middle).
After the bug has been triggered, use-after-free reads will occur in lock_get_status() when userspace reads /proc/locks. This can likely be used to read arbitrary kernel memory, but can't corrupt kernel memory.
Fix it by calling locks_remove_posix() instead, which is designed to reliably get rid of POSIX locks associated with the given file and files_struct and is also used by filp_flush().
From the CVE record · Linux
A race between fcntl_setlk() and close() can leave a POSIX lock behind, leading to use-after-free reads when userspace reads /proc/locks. A local user may be able to read arbitrary kernel memory, but the issue cannot corrupt kernel memory.
Engineers running the Linux kernel should check their installations; affected versions were not specified.