Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-89480: nvme-tcp: reject a read that transferred too few bytes

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12, 832a685efeb5d925ee7d30011d2dbe45f81447a3, 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12, 832a685efeb5d925ee7d30011d2dbe45f81447a3, 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: reject a read that transferred too few bytes nvme_tcp_recv_data() completes a request once the current C2HData PDU has been consumed. Nothing compares the total bytes received against the length the command asked for: struct nvme_tcp_request has no receive-side counter, queue->data_remaining is per queue, and blk_mq_end_request() completes for blk_rq_bytes(rq) unconditionally with no residual concept anywhere above. A controller can therefore answer a 4096-byte read with 512 bytes and have it reported as a complete read; user space then gets 4096 bytes of which 3584 are whatever was already in the page. I reproduced that with a test target. Count the bytes received and refuse to complete a successful read whose count does not match, at the two NVME_TCP_F_DATA_SUCCESS paths and in nvme_tcp_process_nvme_cqe(). The success test shifts req->status right by one, because the driver keeps the wire value there and shifts it on completion, so the check must see what the completion path will see. Only REQ_OP_READ is checked, because there the length comes from the sectors the request covers; a passthrough command is built by its submitter, which picks both command and buffer, so the kernel has nothing to compare against.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 19, 2026
EPSS
0.4% · 35th percentile
CWE
—

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-89480

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.0affected
    • 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before a5c1bb0fb1bab2f24a081339c145870697f6d220affected · git
    • 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before aa107e3a68f4af177d60f2d87679e7f67179a36caffected · git
    • 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before fca3ebb63e5c82561cd9934365dcc0d068008006affected · git
    • 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before 99066cf9bba175f610ceb61a35f6fc9fbc33ff65affected · git
    • 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3affected · git
    • 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before 832a685efeb5d925ee7d30011d2dbe45f81447a3affected · git
    • 3f2304f8c6d6ed97849057bd16fee99e434ca796 and later · before 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12affected · git
    • before 5.0not affected · semver
    • 5.15.221 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.61.1.el10_26.12.0-211.61.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-89478Sep 11, 2026 · sctp: drop a chunk if its transport was removed
    39Monitor
  • ← EarlierCVE-2026-89479Sep 11, 2026 · sctp: stop processing a packet once its association is deleted
    39Monitor
  • Later →CVE-2026-89481Sep 11, 2026 · nvme-tcp: fix host memory disclosure on R2T for a read command
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12Vendor (CNA)
Linux Linux832a685efeb5d925ee7d30011d2dbe45f81447a3Vendor (CNA)
Linux Linux8a02ad98798fd01f51f648c1fdd8f3c9d07195d3Vendor (CNA)
Linux Linux99066cf9bba175f610ceb61a35f6fc9fbc33ff65Vendor (CNA)
Linux Linuxa5c1bb0fb1bab2f24a081339c145870697f6d220Vendor (CNA)
Linux Linuxaa107e3a68f4af177d60f2d87679e7f67179a36cVendor (CNA)
Linux Linuxfca3ebb63e5c82561cd9934365dcc0d068008006Vendor (CNA)
almalinux:bpftool4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.168.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.168.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.168.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.168.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.168.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.168.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.168.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.168.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.168.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+6

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records