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

> A race condition in Linux kernel file locking allows attackers to read arbitrary kernel memory via use-after-free when accessing /proc/locks.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-41012, DEBIAN-CVE-2024-41012, GHSA-c77m-wh63-vhch, UBUNTU-CVE-2024-41012

## What is CVE-2024-41012?

CVE-2024-41012 is a high-severity use after free vulnerability in Linux kernel, published on 23 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-41012?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-41012?

Apply the vendor's patch.

## Is CVE-2024-41012 being exploited?

There is no known exploitation of CVE-2024-41012 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41012 and fix it if it is affected.

What it is: CVE-2024-41012 is a high-severity use after free vulnerability in Linux kernel, published on 23 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41012 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-41012/ (Markdown: https://insights.sbomify.com/CVE-2024-41012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41012
- OSV: https://osv.dev/vulnerability/CVE-2024-41012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41012/
Summaries are generated and may contain mistakes; the official description above is the record.