CVE-2024-41012
Description
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().
How to fix
- linux linux_kernel4.19.319, 5.4.281, 5.10.223, 5.15.164, 6.1.101, 6.6.42, 6.9.9 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| linux linux_kernel | 2.6.13 ≤ v < 4.19.319, 4.20 ≤ v < 5.4.281, 5.5 ≤ v < 5.10.223, 5.11 ≤ v < 5.15.164, 5.16 ≤ v < 6.1.101, 6.2 ≤ v < 6.6.42, 6.7 ≤ v < 6.9.9, 6.10 | 4.19.319, 5.4.281, 5.10.223, 5.15.164, 6.1.101, 6.6.42, 6.9.9 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.