Race Condition Affecting kernel-zfcpdump-core package, versions <0:4.18.0-553.32.1.el8_10


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.04% (6th 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-CENTOS8-KERNELZFCPDUMPCORE-8861978
  • published28 Feb 2025
  • disclosed8 Nov 2024

Introduced: 8 Nov 2024

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

How to fix?

Upgrade Centos:8 kernel-zfcpdump-core to version 0:4.18.0-553.32.1.el8_10 or higher.

NVD Description

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

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

irqchip/gic-v4: Don't allow a VMOVP on a dying VPE

Kunkun Jiang reported that there is a small window of opportunity for userspace to force a change of affinity for a VPE while the VPE has already been unmapped, but the corresponding doorbell interrupt still visible in /proc/irq/.

Plug the race by checking the value of vmapp_count, which tracks whether the VPE is mapped ot not, and returning an error in this case.

This involves making vmapp_count common to both GICv4.1 and its v4.0 ancestor.

CVSS Scores

version 3.1