Uncontrolled Recursion Affecting kernel-zfcpdump-modules package, versions <0:5.14.0-741.14.1.el9_9


Severity

Recommended
high

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.12% (2nd 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-KERNELZFCPDUMPMODULES-22582868
  • published18 Nov 2026
  • disclosed10 Nov 2026

Introduced: 10 Nov 2026

NewCVE-2026-23066  (opens in a new tab)
CWE-674  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:9 kernel-zfcpdump-modules to version 0:5.14.0-741.14.1.el9_9 or higher.
This issue was patched in ALSA-2026:97435.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-zfcpdump-modules package and not the kernel-zfcpdump-modules 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 recvmsg() unconditional requeue

If rxrpc_recvmsg() fails because MSG_DONTWAIT was specified but the call at the front of the recvmsg queue already has its mutex locked, it requeues the call - whether or not the call is already queued. The call may be on the queue because MSG_PEEK was also passed and so the call was not dequeued or because the I/O thread requeued it.

The unconditional requeue may then corrupt the recvmsg queue, leading to things like UAFs or refcount underruns.

Fix this by only requeuing the call if it isn't already on the queue - and moving it to the front if it is already queued. If we don't queue it, we have to put the ref we obtained by dequeuing it.

Also, MSG_PEEK doesn't dequeue the call so shouldn't call rxrpc_notify_socket() for the call if we didn't use up all the data on the queue, so fix that also.

CVSS Base Scores

version 3.1