Race Condition Affecting kernel-zfcpdump-devel package, versions <0:4.18.0-477.67.1.el8_8


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (15th 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 Learn

Learn about Race Condition vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-KERNELZFCPDUMPDEVEL-7684443
  • published14 Aug 2024
  • disclosed30 May 2024

Introduced: 30 May 2024

CVE-2024-36020  (opens in a new tab)
CWE-362  (opens in a new tab)

How to fix?

Upgrade RHEL:8 kernel-zfcpdump-devel to version 0:4.18.0-477.67.1.el8_8 or higher.
This issue was patched in RHSA-2024:5255.

NVD Description

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

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

i40e: fix vf may be used uninitialized in this function warning

To fix the regression introduced by commit 52424f974bc5, which causes servers hang in very hard to reproduce conditions with resets races. Using two sources for the information is the root cause. In this function before the fix bumping v didn't mean bumping vf pointer. But the code used this variables interchangeably, so stale vf could point to different/not intended vf.

Remove redundant "v" variable and iterate via single VF pointer across whole function instead to guarantee VF pointer validity.

CVSS Scores

version 3.1