CVE-2024-41012
Last modified
CVE-2024-41012 is a medium-severity vulnerability rated 6.3/10 on the CVSS scale. 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().. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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().
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 2.6.13, < 4.19.319 | — |
| Linux | Linux Kernel | >= 4.20, < 5.4.281 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.223 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.164 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.101 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.42 | — |
| Linux | Linux Kernel | >= 6.7, < 6.9.9 | — |
| Linux | Linux Kernel | 6.10 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-41012?
How severe is CVE-2024-41012?
How do I fix CVE-2024-41012?
Are you affected by CVE-2024-41012?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
