# CVE-2024-41013: xfs: don't walk off the end of a directory data block

> A crafted XFS image can cause an out-of-bounds read in the Linux kernel, potentially leading to denial of service or information disclosure.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 29 Jul 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-67770, BELL-CVE-2024-41013, DEBIAN-CVE-2024-41013, GHSA-mr66-qfpc-4h9r, ROOT-OS-DEBIAN-11-CVE-2024-41013, ROOT-OS-DEBIAN-12-CVE-2024-41013, ROOT-OS-UBUNTU-2204-CVE-2024-41013, UBUNTU-CVE-2024-41013

## What is CVE-2024-41013?

CVE-2024-41013 is a high-severity memory corruption vulnerability in Linux kernel, published on 29 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:

xfs: don't walk off the end of a directory data block

This adds sanity checks for xfs_dir2_data_unused and xfs_dir2_data_entry
to make sure don't stray beyond valid memory region. Before patching, the
loop simply checks that the start offset of the dup and dep is within the
range. So in a crafted image, if last entry is xfs_dir2_data_unused, we
can change dup->length to dup->length-1 and leave 1 byte of space. In the
next traversal, this space will be considered as dup or dep. We may
encounter an out of bound read when accessing the fixed members.

In the patch, we make sure that the remaining bytes large enough to hold
an unused entry before accessing xfs_dir2_data_unused and
xfs_dir2_data_unused is XFS_DIR2_DATA_ALIGN byte aligned. We also make
sure that the remaining bytes large enough to hold a dirent with a
single-byte name before accessing xfs_dir2_data_entry.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-41013 being exploited?

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

What it is: CVE-2024-41013 is a high-severity memory corruption vulnerability in Linux kernel, published on 29 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-41013 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-41013/ (Markdown: https://insights.sbomify.com/CVE-2024-41013/index.md)
```

## Sources

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

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