Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-52989

9.8 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers Currently, when nvmet_tcp_build_pdu_iovec() detects an o…

Published Jun 24, 2026CWE-908EPSS 0.36%

Overview

CVE-2026-52989 is a critical-severity vulnerability. It was published on June 24, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

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

nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers

Currently, when nvmet_tcp_build_pdu_iovec() detects an out-of-bounds

PDU length or offset, it triggers nvmet_tcp_fatal_error(cmd->queue)

and returns early. However, because the function returns void, the

callers are entirely unaware that a fatal error has occurred and

that the cmd->recv_msg.msg_iter was left uninitialized.

Callers such as nvmet_tcp_handle_h2c_data_pdu() proceed to blindly

overwrite the queue state with queue->rcv_state = NVMET_TCP_RECV_DATA

Consequently, the socket receiving loop may attempt to read incoming

network data into the uninitialized iterator.

Fix this by shifting the error handling responsibility to the callers.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/046fa5c72d15cd8e2d592e275697ea399d8f76b0Refgit.kernel.org/stable/c/3df42a854686fa06484e37ac1a3931c8e3e3453cRefgit.kernel.org/stable/c/c2a11441538bdbbc5aa003f190995eba93a89b88Refgit.kernel.org/stable/c/d7c8f95f599b3b38a717d2e771c3f8c174f657c3Refgit.kernel.org/stable/c/ea8e356acb165cb1fd75537a52e1f66e5e76c538Refgit.kernel.org/stable/c/f9204a2b78dd18374d3bcf9bf93d9021ce22de1bRefaccess.redhat.com/security/cve/CVE-2026-52989Refbugzilla.redhat.com/show_bug.cgi?id=2492443Refsecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52989.json

How CyberStrike helps

Frequently asked questions

What is CVE-2026-52989?

CVE-2026-52989 is a critical-severity vulnerability. It was published on June 24, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2026-52989?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-52989?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-52989?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-52989 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999