Use of Uninitialized Variable The advisory has been revoked - it doesn't affect any version of package kernel-64k-debug-devel  (opens in a new tab)


Threat Intelligence

EPSS
0.73% (55th 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-CENTOS10-KERNEL64KDEBUGDEVEL-20896341
  • published14 Oct 2026
  • disclosed17 Sept 2026

Introduced: 17 Sep 2026

CVE-2026-90104  (opens in a new tab)
CWE-457  (opens in a new tab)

Amendment

The Centos security team deemed this advisory irrelevant for Centos:10.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-64k-debug-devel package and not the kernel-64k-debug-devel package as distributed by Centos.

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

NFSv4.1: zero referring call lists before decoding

decode_cb_sequence_args() allocates csa_rclists with kmalloc_objs(), so each referring_call_list starts uninitialized. decode_rc_list() assigns rcl_refcalls only when rcl_nrefcalls is nonzero. A valid list with zero referring calls therefore leaves the pointer uninitialized, and nfs4_callback_sequence() later passes stale slab contents to kfree().

Allocate csa_rclists with kzalloc_objs() so every rcl_refcalls member is NULL from the beginning, including valid empty referring call lists.