---
title: "CVE-2026-89969: Linux Kernel nvmet-tcp - Out-of-Bounds Write"
description: "Linux kernel nvmet-tcp contains an out-of-bounds write vulnerability caused by improper bounds checking when receiving an over-long PDU, letting remote unauthenticated attackers corrupt adjacent kernel memory, exploit requires sending crafted PDU."
url: https://panop.io/threat-heartbeat/CVE-2026-89969/
---

# CVE-2026-89969 Linux Kernel nvmet-tcp - Out-of-Bounds Write

Linux kernel nvmet-tcp contains an out-of-bounds write vulnerability caused by improper bounds checking when receiving an over-long PDU, letting remote unauthenticated attackers corrupt adjacent kernel memory, exploit requires sending crafted PDU.

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-89969)

## Details

Type

Out-of-Bounds Write

Impact

Privilege Escalation, 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

16 September 2026

Updated

15 October 2026

## Vendor fix

Update to the latest Linux kernel version containing the fix.

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-89969](https://nvd.nist.gov/vuln/detail/CVE-2026-89969)
- [https://git.kernel.org/stable/c/dbc4acbdb3ca8c81441368ad7409b8f77d4de8f6](https://git.kernel.org/stable/c/dbc4acbdb3ca8c81441368ad7409b8f77d4de8f6)
- [https://git.kernel.org/stable/c/14cc5a7e77731497d5bea70f3bb05df7eda982e4](https://git.kernel.org/stable/c/14cc5a7e77731497d5bea70f3bb05df7eda982e4)
- [https://git.kernel.org/stable/c/3a385e0c39efbe34db8edd95900c123113ae3450](https://git.kernel.org/stable/c/3a385e0c39efbe34db8edd95900c123113ae3450)
- [https://git.kernel.org/stable/c/4f84d42c53c49557fb1ef285c683b0a81b576c74](https://git.kernel.org/stable/c/4f84d42c53c49557fb1ef285c683b0a81b576c74)
- [https://git.kernel.org/stable/c/58dc6035b79c4c73c0cbf9ec9f68a7f117b2b3e6](https://git.kernel.org/stable/c/58dc6035b79c4c73c0cbf9ec9f68a7f117b2b3e6)
- [https://git.kernel.org/stable/c/a3f0bcfbaf3312a5754d1ce020a07d394669eb25](https://git.kernel.org/stable/c/a3f0bcfbaf3312a5754d1ce020a07d394669eb25)
- [https://git.kernel.org/stable/c/cf5f39d2b58f97e0cd1829c4a6aeef17f1607cca](https://git.kernel.org/stable/c/cf5f39d2b58f97e0cd1829c4a6aeef17f1607cca)
- [https://git.kernel.org/stable/c/d95d342bc0ea82dc79e6362b2f1f997431750e4c](https://git.kernel.org/stable/c/d95d342bc0ea82dc79e6362b2f1f997431750e4c)

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