CVE-2024-41014

About vulnerability

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 product:

AlmaLinux 9.2 ESU , CentOS 6 ELS , CentOS 7 ELS , CentOS 8.4 ELS , CentOS 8.5 ELS , CentOS Stream 8 ELS , CloudLinux 6 ELS , CloudLinux 7 ELS , Oracle Linux 6 ELS , Oracle Linux 7 ELS , RHEL 7 ELS , TuxCare 9.6 ESU , Ubuntu 16.04 ELS , Ubuntu 18.04 ELS , Ubuntu 20.04 ELS

Affected packages:

kernel @ 3.10.0 (+16 more)

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.

Live-patch status from KernelCare for each operating system.