CVE-2024-41012

MEDIUM EPSS 12.5%
Published Jul 23, 20241y ago · Modified Jun 17, 20261w ago
6.3 CVSS 3.1
Medium
Find Similar
Published Jul 23, 2024 1y ago
Last Modified Jun 17, 2026 1w ago

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

CVSS Details

Base Score
6.3
Exploitability
1.0
Impact
5.2
Vector string
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
Attack Vector Local
Attack Complexity High
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality High
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
12.5% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-416 Use After Free Memory Safety

Affected Products 13

VendorProductVersionRange
linuxlinux_kernel*≥2.6.13  –  <4.19.319
linuxlinux_kernel*≥4.20  –  <5.4.281
linuxlinux_kernel*≥5.5  –  <5.10.223
linuxlinux_kernel*≥5.11  –  <5.15.164
linuxlinux_kernel*≥5.16  –  <6.1.101
linuxlinux_kernel*≥6.2  –  <6.6.42
linuxlinux_kernel*≥6.7  –  <6.9.9
linuxlinux_kernel6.10any
linuxlinux_kernel6.10any
linuxlinux_kernel6.10any
linuxlinux_kernel6.10any
linuxlinux_kernel6.10any
linuxlinux_kernel6.10any

References 9

  • git.kernel.org https://git.kernel.org/stable/c/3cad1bc010416c6dd780643476bc59ed742436b9
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/52c87ab18c76c14d7209646ccb3283b3f5d87b22
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/5661b9c7ec189406c2dde00837aaa4672efb6240
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/5f5d0799eb0a01d550c21b7894e26b2d9db55763
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b6d223942c34057fdfd8f149e763fa823731b224
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/d30ff33040834c3b9eee29740acd92f9c7ba2250
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/dc2ce1dfceaa0767211a9d963ddb029ab21c4235
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/ef8fc41cd6f95f9a4a3470f085aecf350569a0b3
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Remediation

  • git.kernel.org https://git.kernel.org/stable/c/3cad1bc010416c6dd780643476bc59ed742436b9
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/52c87ab18c76c14d7209646ccb3283b3f5d87b22
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/5661b9c7ec189406c2dde00837aaa4672efb6240
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/5f5d0799eb0a01d550c21b7894e26b2d9db55763
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b6d223942c34057fdfd8f149e763fa823731b224
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/d30ff33040834c3b9eee29740acd92f9c7ba2250
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/dc2ce1dfceaa0767211a9d963ddb029ab21c4235
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/ef8fc41cd6f95f9a4a3470f085aecf350569a0b3
    Patch