# CVE-2024-41014: xfs: add bounds checking to xlog_recover_process_data

> A local attacker can trigger an out-of-bounds read in the Linux kernel XFS filesystem by mounting a crafted image, potentially causing a crash or leaking memory.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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:** AZL-57782, BELL-CVE-2024-41014, DEBIAN-CVE-2024-41014, GHSA-jfpf-jvq3-6jwv, ROOT-OS-DEBIAN-11-CVE-2024-41014, ROOT-OS-UBUNTU-2204-CVE-2024-41014, UBUNTU-CVE-2024-41014

## What is CVE-2024-41014?

CVE-2024-41014 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, and only if a user opens a file or follows a link.

### Official description

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

xfs: add bounds checking to xlog_recover_process_data

There is a lack of verification of the space occupied by fixed members
of xlog_op_header in the xlog_recover_process_data.

We can create a crafted image to trigger an out of bounds read by
following these steps:
    1) Mount an image of xfs, and do some file operations to leave records
    2) Before umounting, copy the image for subsequent steps to simulate
       abnormal exit. Because umount will ensure that tail_blk and
       head_blk are the same, which will result in the inability to enter
       xlog_recover_process_data
    3) Write a tool to parse and modify the copied image in step 2
    4) Make the end of the xlog_op_header entries only 1 byte away from
       xlog_rec_header->h_size
    5) xlog_rec_header->h_num_logops++
    6) Modify xlog_rec_header->h_crc

Fix:
Add a check to make sure there is sufficient space to access fixed members
of xlog_op_header.

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

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-41014 being exploited?

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

What it is: CVE-2024-41014 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, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-41014 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-41014/ (Markdown: https://insights.sbomify.com/CVE-2024-41014/index.md)
```

## Sources

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

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