CVE-2026-63971 Affecting kernel-zfcpdump-modules-core package, versions <0:5.14.0-687.47.1.el9_8


Severity

Recommended
high

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-KERNELZFCPDUMPMODULESCORE-19903019
  • published18 Sept 2026
  • disclosed14 Sept 2026

Introduced: 14 Sep 2026

NewCVE-2026-63971  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:9 kernel-zfcpdump-modules-core to version 0:5.14.0-687.47.1.el9_8 or higher.
This issue was patched in ALSA-2026:67150.

NVD Description

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

sctp: fix race between sctp_wait_for_connect and peeloff

sctp_wait_for_connect() drops and re-acquires the socket lock while waiting for the association to reach ESTABLISHED state. During this window, another thread can peeloff the association to a new socket via getsockopt(SCTP_SOCKOPT_PEELOFF), changing asoc->base.sk. After re-acquiring the old socket lock, sctp_wait_for_connect() returns success without noticing the migration — the caller then accesses the association under the wrong lock in sctp_datamsg_from_user().

Add the same sk != asoc->base.sk check that sctp_wait_for_sndbuf() already has, returning an error if the association was migrated while we slept.

CVSS Base Scores

version 3.1