---
title: "CVE-2026-89482: Linux Kernel nvme-tcp - Memory Corruption"
description: "Linux kernel nvme-tcp contains a memory corruption vulnerability caused by improper validation of C2HData based on blk_rq_payload_bytes() without checking blk_rq_nr_phys_segments(), letting attackers cause wild memory access and kernel crash, exploit requires crafted network packets targeting WRITE_ZEROES commands."
url: https://panop.io/threat-heartbeat/CVE-2026-89482/
---

# CVE-2026-89482 Linux Kernel nvme-tcp - Memory Corruption

Linux kernel nvme-tcp contains a memory corruption vulnerability caused by improper validation of C2HData based on blk\_rq\_payload\_bytes() without checking blk\_rq\_nr\_phys\_segments(), letting attackers cause wild memory access and kernel crash, exploit requires crafted network packets targeting WRITE\_ZEROES commands.

CVSS base score 9.8 /10

Critical

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.71% chance of exploitation in 30 days

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

## Details

Type

Memory Corruption

Impact

Denial Of Service

CVSS vector

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

Published

11 September 2026

Updated

15 October 2026

## Vendor fix

Update to Linux kernel version 7.2.0-rc5-NVMETCP-gf5098b6bae76 or later where the issue is fixed.

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-89482](https://nvd.nist.gov/vuln/detail/CVE-2026-89482)
- [https://git.kernel.org/stable/c/b36161701cb366f416afdcf70771d432a7c74753](https://git.kernel.org/stable/c/b36161701cb366f416afdcf70771d432a7c74753)
- [https://git.kernel.org/stable/c/32ea8ce96b9bd797c59c351ce490ffd97adaa8c0](https://git.kernel.org/stable/c/32ea8ce96b9bd797c59c351ce490ffd97adaa8c0)
- [https://git.kernel.org/stable/c/7ed0b61bbc145988be292c4d3ec580aebd8d2bcd](https://git.kernel.org/stable/c/7ed0b61bbc145988be292c4d3ec580aebd8d2bcd)
- [https://git.kernel.org/stable/c/b96e1ff75e5c0ad6e077ac002b1d30b0a2b49528](https://git.kernel.org/stable/c/b96e1ff75e5c0ad6e077ac002b1d30b0a2b49528)
- [https://git.kernel.org/stable/c/dd8906bb8f8d5bf1c9f861e1382c82b87bfe7cab](https://git.kernel.org/stable/c/dd8906bb8f8d5bf1c9f861e1382c82b87bfe7cab)
- [https://git.kernel.org/stable/c/3a4aa9e6ad3e35f8e24d5eaf38ee4d437075fb36](https://git.kernel.org/stable/c/3a4aa9e6ad3e35f8e24d5eaf38ee4d437075fb36)
- [https://git.kernel.org/stable/c/641ad3a30ba560f0a9a610376c568d7b75d2a2aa](https://git.kernel.org/stable/c/641ad3a30ba560f0a9a610376c568d7b75d2a2aa)
- [https://git.kernel.org/stable/c/6a01b58263108eaf9869bb6f82f07709240c6589](https://git.kernel.org/stable/c/6a01b58263108eaf9869bb6f82f07709240c6589)

[← 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)