Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-41012filelock: Remove locks reliably when fcntl/close race is detected

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

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-41012, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium6.3CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected c293621bbf678a3d85e3ed721c3921c8a670610d – < d30ff33040834c3b9eee29740acd92f9c7ba2250
    • affected c293621bbf678a3d85e3ed721c3921c8a670610d – < dc2ce1dfceaa0767211a9d963ddb029ab21c4235
    • affected c293621bbf678a3d85e3ed721c3921c8a670610d – < 5661b9c7ec189406c2dde00837aaa4672efb6240
    • affected c293621bbf678a3d85e3ed721c3921c8a670610d – < 52c87ab18c76c14d7209646ccb3283b3f5d87b22
    • affected c293621bbf678a3d85e3ed721c3921c8a670610d – < ef8fc41cd6f95f9a4a3470f085aecf350569a0b3
    • affected c293621bbf678a3d85e3ed721c3921c8a670610d – < 5f5d0799eb0a01d550c21b7894e26b2d9db55763
    • affected c293621bbf678a3d85e3ed721c3921c8a670610d – < b6d223942c34057fdfd8f149e763fa823731b224
    • affected c293621bbf678a3d85e3ed721c3921c8a670610d – < 3cad1bc010416c6dd780643476bc59ed742436b9
  • Linux · Linux

    • affected 2.6.13
    • unaffected < 2.6.13
    • unaffected 4.19.319 – ≤ 4.19.*
    • unaffected 5.4.281 – ≤ 5.4.*
    • unaffected 5.10.223 – ≤ 5.10.*
    • unaffected 5.15.164 – ≤ 5.15.*
    • unaffected 6.1.101 – ≤ 6.1.*
    • unaffected 6.6.42 – ≤ 6.6.*
    • unaffected 6.9.9 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-41012 badge
[![CVE-2024-41012](https://cveledger.app/badge/CVE-2024-41012.svg)](https://cveledger.app/cve/CVE-2024-41012)

Record last updated .