# CVE-2024-41034: nilfs2: fix kernel bug on rename operation of broken directory

> A local attacker can cause a kernel crash by renaming a broken directory in the nilfs2 filesystem, leading to denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Jul 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-41034, DEBIAN-CVE-2024-41034, GHSA-v738-pvhm-mhvp, UBUNTU-CVE-2024-41034

## What is CVE-2024-41034?

CVE-2024-41034 is a high-severity vulnerability in Linux kernel, published on 29 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

nilfs2: fix kernel bug on rename operation of broken directory

Syzbot reported that in rename directory operation on broken directory on
nilfs2, __block_write_begin_int() called to prepare block write may fail
BUG_ON check for access exceeding the folio/page size.

This is because nilfs_dotdot(), which gets parent directory reference
entry ("..") of the directory to be moved or renamed, does not check
consistency enough, and may return location exceeding folio/page size for
broken directories.

Fix this issue by checking required directory entries ("." and "..") in
the first chunk of the directory in nilfs_dotdot().

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-41034 being exploited?

There is no known exploitation of CVE-2024-41034 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-41034 and fix it if it is affected.

What it is: CVE-2024-41034 is a high-severity vulnerability in Linux kernel, published on 29 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-41034 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-41034/ (Markdown: https://insights.sbomify.com/CVE-2024-41034/index.md)
```

## Sources

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

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