---
title: "CVE-2026-89480: Linux Kernel nvme-tcp - Data Integrity Vulnerability"
description: "Linux kernel nvme-tcp contains a data integrity vulnerability caused by improper validation of read byte count in nvme_tcp_recv_data(), letting attackers cause incomplete reads to be reported as complete, exploit requires malicious NVMe controller."
url: https://panop.io/threat-heartbeat/CVE-2026-89480/
---

# CVE-2026-89480 Linux Kernel nvme-tcp - Data Integrity Vulnerability

Linux kernel nvme-tcp contains a data integrity vulnerability caused by improper validation of read byte count in nvme\_tcp\_recv\_data(), letting attackers cause incomplete reads to be reported as complete, exploit requires malicious NVMe controller.

CVSS base score 7.5 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.41% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-89480)

## Details

Type

Data Integrity Vulnerability

Impact

Data Tampering, Information Disclosure

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Published

11 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix for nvme-tcp read byte count validation.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-89480](https://nvd.nist.gov/vuln/detail/CVE-2026-89480)
- [https://git.kernel.org/stable/c/a5c1bb0fb1bab2f24a081339c145870697f6d220](https://git.kernel.org/stable/c/a5c1bb0fb1bab2f24a081339c145870697f6d220)
- [https://git.kernel.org/stable/c/aa107e3a68f4af177d60f2d87679e7f67179a36c](https://git.kernel.org/stable/c/aa107e3a68f4af177d60f2d87679e7f67179a36c)
- [https://git.kernel.org/stable/c/fca3ebb63e5c82561cd9934365dcc0d068008006](https://git.kernel.org/stable/c/fca3ebb63e5c82561cd9934365dcc0d068008006)
- [https://git.kernel.org/stable/c/7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12](https://git.kernel.org/stable/c/7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12)
- [https://git.kernel.org/stable/c/832a685efeb5d925ee7d30011d2dbe45f81447a3](https://git.kernel.org/stable/c/832a685efeb5d925ee7d30011d2dbe45f81447a3)
- [https://git.kernel.org/stable/c/8a02ad98798fd01f51f648c1fdd8f3c9d07195d3](https://git.kernel.org/stable/c/8a02ad98798fd01f51f648c1fdd8f3c9d07195d3)
- [https://git.kernel.org/stable/c/99066cf9bba175f610ceb61a35f6fc9fbc33ff65](https://git.kernel.org/stable/c/99066cf9bba175f610ceb61a35f6fc9fbc33ff65)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)