Use After Free Affecting kernel-headers package, versions <0:4.18.0-553.22.1.el8_10

Note: Versions mentioned in the description apply only to the upstream kernel-headers package and not the kernel-headers package as distributed by Centos. See How to fix? for Centos:8 relevant fixed versions and status.

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().

• https://access.redhat.com/security/cve/CVE-2024-41012
• https://git.kernel.org/stable/c/3cad1bc010416c6dd780643476bc59ed742436b9
• https://git.kernel.org/stable/c/52c87ab18c76c14d7209646ccb3283b3f5d87b22
• https://git.kernel.org/stable/c/5661b9c7ec189406c2dde00837aaa4672efb6240
• https://git.kernel.org/stable/c/5f5d0799eb0a01d550c21b7894e26b2d9db55763
• https://git.kernel.org/stable/c/b6d223942c34057fdfd8f149e763fa823731b224
• https://git.kernel.org/stable/c/d30ff33040834c3b9eee29740acd92f9c7ba2250
• https://git.kernel.org/stable/c/dc2ce1dfceaa0767211a9d963ddb029ab21c4235
• https://git.kernel.org/stable/c/ef8fc41cd6f95f9a4a3470f085aecf350569a0b3