filelock: Remove locks reliably when fcntl/close race is detected
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3cad1bc010416c6dd780643476bc59ed742436b9, Kernel 52c87ab18c76c14d7209646ccb3283b3f5d87b22, Kernel 5661b9c7ec189406c2dde00837aaa4672efb6240 and 5 more.
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().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.13, >=c293621bbf678a3d85e3ed721c3921c8a670610d <3cad1bc010416c6dd780643476bc59ed742436b9, >=c293621bbf678a3d85e3ed721c3921c8a670610d <52c87ab18c76c14d7209646ccb3283b3f5d87b22, >=c293621bbf678a3d85e3ed721c3921c8a670610d <5661b9c7ec189406c2dde00837aaa4672efb6240, >=c293621bbf678a3d85e3ed721c3921c8a670610d <5f5d0799eb0a01d550c21b7894e26b2d9db55763, >=c293621bbf678a3d85e3ed721c3921c8a670610d <b6d223942c34057fdfd8f149e763fa823731b224, >=c293621bbf678a3d85e3ed721c3921c8a670610d <d30ff33040834c3b9eee29740acd92f9c7ba2250, >=c293621bbf678a3d85e3ed721c3921c8a670610d <dc2ce1dfceaa0767211a9d963ddb029ab21c4235, >=c293621bbf678a3d85e3ed721c3921c8a670610d <ef8fc41cd6f95f9a4a3470f085aecf350569a0b3 | 3cad1bc010416c6dd780643476bc59ed742436b9, 52c87ab18c76c14d7209646ccb3283b3f5d87b22, 5661b9c7ec189406c2dde00837aaa4672efb6240, 5f5d0799eb0a01d550c21b7894e26b2d9db55763, b6d223942c34057fdfd8f149e763fa823731b224, d30ff33040834c3b9eee29740acd92f9c7ba2250, dc2ce1dfceaa0767211a9d963ddb029ab21c4235, ef8fc41cd6f95f9a4a3470f085aecf350569a0b3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket