CVE-2026-52989

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-24. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 15, 2026

Advisory Details (9)

Auto-updated Jul 25, 2026
Patch available. Sources: redhat.
redhat

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52989.json
redhat

2492443 – (CVE-2026-52989) CVE-2026-52989 kernel: nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers

https://bugzilla.redhat.com/show_bug.cgi?id=2492443
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-52989
generic

nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9204a2b78dd18374d3bcf9bf93d9021ce22de1b
generic

nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea8e356acb165cb1fd75537a52e1f66e5e76c538
generic

nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d7c8f95f599b3b38a717d2e771c3f8c174f657c3
generic

nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c2a11441538bdbbc5aa003f190995eba93a89b88
generic

nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3df42a854686fa06484e37ac1a3931c8e3e3453c
generic

nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/046fa5c72d15cd8e2d592e275697ea399d8f76b0

Vendor Advisories for CVE-2026-52989(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-26ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-07-26ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-07-26ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-07-26ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-07-26ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-26ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-07-26ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-07-26ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-07-26ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-07-26ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-07-26ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-07-26ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-07-26ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-07-26ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-07-26ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(15)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 16× in last 7d / 173× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 177 total refreshes for this CVE.

  1. 2026-07-27 06:10 UTCVendor advisory
  2. 2026-07-27 06:10 UTCGHSA enrichment
  3. 2026-07-27 01:11 UTCVendor advisory
  4. 2026-07-27 01:11 UTCGHSA enrichment
  5. 2026-07-26 20:04 UTCVendor advisory
  6. 2026-07-26 20:04 UTCGHSA enrichment
  7. 2026-07-26 15:40 UTCEG score recompute
  8. 2026-07-26 15:40 UTCVendor advisory
  9. 2026-07-26 15:40 UTCGHSA enrichment
  10. 2026-07-26 14:54 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 03:19 UTCEG score recompute
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-20 17:08 UTCEPSS rescore
  17. 2026-07-19 14:31 UTCEPSS rescore
  18. 2026-07-19 14:31 UTCEPSS rescore
  19. 2026-07-19 02:29 UTCEPSS rescore
  20. 2026-07-18 10:04 UTCEPSS rescore
  21. 2026-07-17 03:42 UTCVendor advisory
  22. 2026-07-17 03:42 UTCGHSA enrichment
  23. 2026-07-16 23:20 UTCVendor advisory
  24. 2026-07-16 23:20 UTCGHSA enrichment
  25. 2026-07-16 18:58 UTCVendor advisory
Show 75 more
  1. 2026-07-16 18:58 UTCGHSA enrichment
  2. 2026-07-16 17:03 UTCEPSS rescore
  3. 2026-07-16 14:35 UTCGHSA enrichment
  4. 2026-07-16 10:08 UTCVendor advisory
  5. 2026-07-16 10:08 UTCGHSA enrichment
  6. 2026-07-16 05:45 UTCVendor advisory
  7. 2026-07-16 05:45 UTCGHSA enrichment
  8. 2026-07-16 01:21 UTCVendor advisory
  9. 2026-07-16 01:21 UTCGHSA enrichment
  10. 2026-07-15 20:58 UTCVendor advisory
  11. 2026-07-15 20:58 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:22 UTCVendor advisory
  15. 2026-07-15 16:22 UTCGHSA enrichment
  16. 2026-07-15 12:00 UTCVendor advisory
  17. 2026-07-15 12:00 UTCGHSA enrichment
  18. 2026-07-15 07:19 UTCVendor advisory
  19. 2026-07-15 07:19 UTCGHSA enrichment
  20. 2026-07-15 02:56 UTCVendor advisory
  21. 2026-07-15 02:56 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-14 22:33 UTCVendor advisory
  25. 2026-07-14 22:33 UTCGHSA enrichment
  26. 2026-07-14 18:10 UTCVendor advisory
  27. 2026-07-14 18:10 UTCGHSA enrichment
  28. 2026-07-14 13:29 UTCVendor advisory
  29. 2026-07-14 13:28 UTCGHSA enrichment
  30. 2026-07-14 09:06 UTCVendor advisory
  31. 2026-07-14 09:05 UTCGHSA enrichment
  32. 2026-07-14 04:42 UTCVendor advisory
  33. 2026-07-14 04:42 UTCGHSA enrichment
  34. 2026-07-14 00:19 UTCGHSA enrichment
  35. 2026-07-13 22:31 UTCEPSS rescore
  36. 2026-07-13 19:55 UTCGHSA enrichment
  37. 2026-07-13 15:32 UTCGHSA enrichment
  38. 2026-07-13 11:07 UTCGHSA enrichment
  39. 2026-07-13 06:43 UTCGHSA enrichment
  40. 2026-07-13 06:13 UTCEPSS rescore
  41. 2026-07-13 06:13 UTCEPSS rescore
  42. 2026-07-13 02:13 UTCVendor advisory
  43. 2026-07-13 02:13 UTCGHSA enrichment
  44. 2026-07-12 21:50 UTCVendor advisory
  45. 2026-07-12 21:50 UTCGHSA enrichment
  46. 2026-07-12 17:27 UTCVendor advisory
  47. 2026-07-12 17:27 UTCGHSA enrichment
  48. 2026-07-12 13:05 UTCVendor advisory
  49. 2026-07-12 13:05 UTCGHSA enrichment
  50. 2026-07-12 08:43 UTCVendor advisory
  51. 2026-07-12 08:42 UTCGHSA enrichment
  52. 2026-07-12 05:46 UTCEPSS rescore
  53. 2026-07-12 04:19 UTCVendor advisory
  54. 2026-07-12 04:19 UTCGHSA enrichment
  55. 2026-07-11 23:57 UTCVendor advisory
  56. 2026-07-11 23:57 UTCGHSA enrichment
  57. 2026-07-11 19:34 UTCVendor advisory
  58. 2026-07-11 19:34 UTCGHSA enrichment
  59. 2026-07-11 15:12 UTCVendor advisory
  60. 2026-07-11 15:12 UTCGHSA enrichment
  61. 2026-07-11 10:46 UTCVendor advisory
  62. 2026-07-11 10:46 UTCGHSA enrichment
  63. 2026-07-11 08:27 UTCEPSS rescore
  64. 2026-07-11 08:27 UTCEPSS rescore
  65. 2026-07-11 06:23 UTCVendor advisory
  66. 2026-07-11 06:23 UTCGHSA enrichment
  67. 2026-07-11 01:56 UTCVendor advisory
  68. 2026-07-11 01:56 UTCGHSA enrichment
  69. 2026-07-10 21:32 UTCVendor advisory
  70. 2026-07-10 21:32 UTCGHSA enrichment
  71. 2026-07-10 17:09 UTCVendor advisory
  72. 2026-07-10 17:09 UTCGHSA enrichment
  73. 2026-07-10 12:47 UTCVendor advisory
  74. 2026-07-10 12:47 UTCGHSA enrichment
  75. 2026-07-10 08:21 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-52989?
CVE-2026-52989 is a critical vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: propagate nvmettcpbuildpduiovec() errors to its callers Currently, when nvmettcpbuildpduiovec() detects an out-of-bounds PDU length or offset, it triggers nvmettcpfatal_error(cmd->queue) and returns early. However,…
When was CVE-2026-52989 disclosed?
CVE-2026-52989 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52989 actively exploited?
CVE-2026-52989 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.2% of all scored CVEs.
What is the CVSS score of CVE-2026-52989?
CVE-2026-52989 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-52989?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52989, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-52989

Explore →

Is Your Infrastructure Affected by CVE-2026-52989?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs