NULL Pointer Dereference Affecting kernel-64k-modules-extra package, versions <0:6.12.0-124.38.1.el10_1


Severity

Recommended
medium

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.05% (15th 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-ROCKY10-KERNEL64KMODULESEXTRA-15342145
  • published25 Feb 2026
  • disclosed25 Jan 2026

Introduced: 25 Jan 2026

CVE-2026-22998  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:10 kernel-64k-modules-extra to version 0:6.12.0-124.38.1.el10_1 or higher.
This issue was patched in RLSA-2026:2721.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-64k-modules-extra package and not the kernel-64k-modules-extra package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:10 relevant fixed versions and status.

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

nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec

Commit efa56305908b ("nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length") added ttag bounds checking and data_offset validation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate whether the command's data structures (cmd->req.sg and cmd->iov) have been properly initialized before processing H2C_DATA PDUs.

The nvmet_tcp_build_pdu_iovec() function dereferences these pointers without NULL checks. This can be triggered by sending H2C_DATA PDU immediately after the ICREQ/ICRESP handshake, before sending a CONNECT command or NVMe write command.

Attack vectors that trigger NULL pointer dereferences:

  1. H2C_DATA PDU sent before CONNECT → both pointers NULL
  2. H2C_DATA PDU for READ command → cmd->req.sg allocated, cmd->iov NULL
  3. H2C_DATA PDU for uninitialized command slot → both pointers NULL

The fix validates both cmd->req.sg and cmd->iov before calling nvmet_tcp_build_pdu_iovec(). Both checks are required because:

  • Uninitialized commands: both NULL
  • READ commands: cmd->req.sg allocated, cmd->iov NULL
  • WRITE commands: both allocated

CVSS Base Scores

version 3.1