CVE-2024-41014 Affecting kernel-zfcpdump package, versions <0:5.14.0-427.42.1.el9_4


Severity

Recommended
medium

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ROCKY9-KERNELZFCPDUMP-8363696
  • published9 Nov 2024
  • disclosed29 Jul 2024

Introduced: 29 Jul 2024

CVE-2024-41014  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:9 kernel-zfcpdump to version 0:5.14.0-427.42.1.el9_4 or higher.
This issue was patched in RLSA-2024:8617.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-zfcpdump package and not the kernel-zfcpdump package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:9 relevant fixed versions and status.

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.

CVSS Scores

version 3.1