Race Condition Affecting kernel-zfcpdump-devel-matched package, versions <0:5.14.0-611.5.1.el9_7


Severity

Recommended
0.0
medium
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.17% (7th 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-ALMALINUX9-KERNELZFCPDUMPDEVELMATCHED-14061392
  • published20 Nov 2025
  • disclosed11 Nov 2025

Introduced: 11 Nov 2025

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

How to fix?

Upgrade AlmaLinux:9 kernel-zfcpdump-devel-matched to version 0:5.14.0-611.5.1.el9_7 or higher.
This issue was patched in ALSA-2025:20518.

NVD Description

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

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

rxrpc: Fix a race between socket set up and I/O thread creation

In rxrpc_open_socket(), it sets up the socket and then sets up the I/O thread that will handle it. This is a problem, however, as there's a gap between the two phases in which a packet may come into rxrpc_encap_rcv() from the UDP packet but we oops when trying to wake the not-yet created I/O thread.

As a quick fix, just make rxrpc_encap_rcv() discard the packet if there's no I/O thread yet.

A better, but more intrusive fix would perhaps be to rearrange things such that the socket creation is done by the I/O thread.

CVSS Base Scores

version 3.1