Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 49 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89480, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.43% · top 63% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 – < b674af31d044a86bd094ba8bb8f2bb92fb49aac5
    • affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 – < a5c1bb0fb1bab2f24a081339c145870697f6d220
    • affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 – < aa107e3a68f4af177d60f2d87679e7f67179a36c
    • affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 – < fca3ebb63e5c82561cd9934365dcc0d068008006
    • affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 – < 99066cf9bba175f610ceb61a35f6fc9fbc33ff65
    • affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 – < 8a02ad98798fd01f51f648c1fdd8f3c9d07195d3
    • affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 – < 832a685efeb5d925ee7d30011d2dbe45f81447a3
    • affected 3f2304f8c6d6ed97849057bd16fee99e434ca796 – < 7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89480 badge
[![CVE-2026-89480](https://cveledger.app/badge/CVE-2026-89480.svg)](https://cveledger.app/cve/CVE-2026-89480)

Record last updated .