Linux Kernel up to 6.12.66/6.18.6/6.19-rc5 nvmet_tcp_handle_h2c_data_pdu null pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.12.66/6.18.6/6.19-rc5. Impacted is the function nvmet_tcp_handle_h2c_data_pdu. Executing a manipulation can lead to null pointer dereference. This vulnerability is registered as CVE-2026-22998. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.12.66/6.18.6/6.19-rc5. This vulnerability affects the function nvmet_tcp_handle_h2c_data_pdu. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. CVE summarizes:

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

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-22998 since 01/13/2026. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 296541 (Linux Distros Unpatched Vulnerability : CVE-2026-22998), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.67, 6.18.7 or 6.19-rc6 eliminates this vulnerability. Applying the patch 3def5243150716be86599c2a1767c29c68838b6d/374b095e265fa27465f34780e0eb162ff1bef913/32b63acd78f577b332d976aa06b56e70d054cbba is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (296541), EUVD (EUVD-2026-4629) and CERT Bund (WID-SEC-2026-0783). Once again VulDB remains the best source for vulnerability data.

Affected

  • IBM QRadar SIEM

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.6
VulDB Meta Temp Score: 6.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 296541
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-22998

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.67/6.18.7/6.19-rc6
Patch: 3def5243150716be86599c2a1767c29c68838b6d/374b095e265fa27465f34780e0eb162ff1bef913/32b63acd78f577b332d976aa06b56e70d054cbba

Timelineinfo

01/13/2026 CVE reserved
01/25/2026 +12 days Advisory disclosed
01/25/2026 +0 days VulDB entry created
03/19/2026 +53 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-22998 (🔒)
GCVE (CVE): GCVE-0-2026-22998
GCVE (VulDB): GCVE-100-342820
EUVD: 🔒
CERT Bund: WID-SEC-2026-0783 - IBM QRadar SIEM: Mehrere Schwachstellen

Entryinfo

Created: 01/25/2026 15:57
Updated: 03/19/2026 11:36
Changes: 01/25/2026 15:57 (58), 01/26/2026 02:23 (1), 01/26/2026 10:37 (2), 02/26/2026 20:21 (10), 03/18/2026 22:51 (6), 03/19/2026 11:36 (7)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!