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

Published Jul 29, 2024
·
Updated

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

xfs: add bounds checking to xlogrecoverprocessdata

There is a lack of verification of the space occupied by fixed members of xlogopheader in the xlogrecoverprocessdata.

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 tailblk and headblk are the same, which will result in the inability to enter xlogrecoverprocessdata 3) Write a tool to parse and modify the copied image in step 2 4) Make the end of the xlogopheader entries only 1 byte away from xlogrecheader->hsize 5) xlogrecheader->hnumlogops++ 6) Modify xlogrecheader->hcrc

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

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

10 affected componentsFixes available
Linux Linux kernel<6.1.120
Linux Linux kernel>=6.2<6.6.64
Linux Linux kernel>=6.7<6.11
IBM Security Verify Governance<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Software Stack<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Virtual Appliance<=ISVG 10.0.2
IBM Security Verify Governance Identity Manager Container<=ISVG 10.0.2
redhat/kernel<6.11
6.11
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1

Event History

Jul 29, 2024
CVE Published
via MITRE·06:37 AM
Data Sourced
via MITRE·06:37 AM
Description
Data Sourced
via NVD·07:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 23, 2025
Data Sourced
via Launchpad·05:35 PM
Description
May 1, 2025
Data Sourced
via Ubuntu·05:35 PM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-41014?

CVE-2024-41014 has been assigned a medium severity rating due to its potential impact on data integrity.

2

How do I fix CVE-2024-41014?

To fix CVE-2024-41014, upgrade to the kernel version 6.11 or higher from Red Hat.

3

What type of systems are affected by CVE-2024-41014?

CVE-2024-41014 affects systems running specific versions of the Linux kernel that utilize XFS file systems.

4

Is there a workaround for CVE-2024-41014?

Currently, there is no known workaround for CVE-2024-41014; the suggested solution is to apply the version update.

5

What impact does CVE-2024-41014 have on system security?

CVE-2024-41014 could allow for potential exploitation leading to unauthorized access or manipulation of data within affected systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203