CVE-2024-41014

Medium

Elevated severity or exploit probability.

CVSS base

7.1 HIGH

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

EPSS — probability of exploitation (30 days)

0.2%

15.0th percentile

CISA KEV

Not listed

Weakness / dates

CWE-125

Published 2024-07-29 · modified 2026-08-04

CVSS breakdown

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

Attack Vector	L	Local
Attack Complexity	L	Low
Privileges Required	N	None
User Interaction	R	Required
Scope	U	Unchanged
Confidentiality	H	High
Integrity	N	None
Availability	H	High

Timeline

2024-07-29 — Published (NVD)
2026-08-04 — Last modified (NVD)

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.

Affected

linux

References

Official: NVD · CVE.org