CVE-2026-89480

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-11. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-76386 (ENISA EUVD) · GHSA-p53f-q495-p25h (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

October 30, 2026

Advisory Details (4)

Auto-updated Sep 13, 2026
Patch available.
Web page

nvme-tcp: reject a read that transferred too few bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/99066cf9bba175f610ceb61a35f6fc9fbc33ff65
Web page

nvme-tcp: reject a read that transferred too few bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a02ad98798fd01f51f648c1fdd8f3c9d07195d3
Web page

nvme-tcp: reject a read that transferred too few bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/832a685efeb5d925ee7d30011d2dbe45f81447a3
Web page

nvme-tcp: reject a read that transferred too few bytes - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7fa3f73f6c8ddc5f0425b50fb2a626a782ef7d12

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift/ose-rhel-coreos-9:4.22.9.8.202610241758-02026-10-27redhat
redhatkernel-0:5.14.0-687.55.1.el9_82026-10-08redhat
redhatkernel-0:6.12.0-211.61.1.el10_22026-09-28redhat
redhatkernel-rt-0:4.18.0-553.168.1.rt7.509.el8_102026-09-24redhat
redhatkernel-0:4.18.0-553.168.1.el8_102026-09-24redhat
linuxKernel @ 5.10.273 (fixes >=5.0.0)—osv

These rows come from Red Hat and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 239 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 139 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 18:56 UTCOSV refresh
  2. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-20 13:31 UTCEchelonGraph re-scored
  5. 2026-11-20 13:31 UTCVendor advisory
  6. 2026-11-20 13:31 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-11-15 17:03 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  12. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-11-13 13:41 UTCEchelonGraph re-scored
  15. 2026-11-13 13:41 UTCVendor advisory
  16. 2026-11-13 13:41 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  23. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-11-06 13:20 UTCEchelonGraph re-scored
  25. 2026-11-06 13:20 UTCVendor advisory
Show 75 more
  1. 2026-11-06 13:20 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  2. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  8. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-30 13:29 UTCEchelonGraph re-scored
  10. 2026-10-30 13:29 UTCVendor advisory
  11. 2026-10-30 13:29 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-10-30 12:43 UTCEchelonGraph re-scored
  13. 2026-10-30 12:43 UTCVendor advisory
  14. 2026-10-30 12:43 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  17. 2026-10-27 17:55 UTCEchelonGraph re-scored
  18. 2026-10-27 17:55 UTCVendor advisory
  19. 2026-10-27 17:55 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  20. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  21. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  22. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-10-25 13:53 UTCEchelonGraph re-scored
  24. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  26. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  27. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  28. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  29. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  30. 2026-10-19 09:32 UTCEchelonGraph re-scored
  31. 2026-10-19 09:32 UTCVendor advisory
  32. 2026-10-19 09:31 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  33. 2026-10-19 09:04 UTCEchelonGraph re-scored
  34. 2026-10-19 09:04 UTCVendor advisory
  35. 2026-10-19 09:04 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  36. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  37. 2026-10-18 03:02 UTCEchelonGraph re-scored
  38. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  39. 2026-10-16 20:31 UTCEchelonGraph re-scored
  40. 2026-10-16 20:31 UTCVendor advisory
  41. 2026-10-16 20:31 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  42. 2026-10-16 19:36 UTCEchelonGraph re-scored
  43. 2026-10-16 19:36 UTCVendor advisory
  44. 2026-10-16 19:36 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  45. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  46. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  47. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  48. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  49. 2026-10-13 04:56 UTCEchelonGraph re-scored
  50. 2026-10-13 04:56 UTCVendor advisory
  51. 2026-10-13 04:55 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  52. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  53. 2026-10-12 14:48 UTCEchelonGraph re-scored
  54. 2026-10-11 21:37 UTCEchelonGraph re-scored
  55. 2026-10-11 21:37 UTCVendor advisory
  56. 2026-10-11 21:37 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  57. 2026-10-11 19:15 UTCEchelonGraph re-scored
  58. 2026-10-11 16:32 UTCEchelonGraph re-scored
  59. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  60. 2026-10-11 13:47 UTCEchelonGraph re-scored
  61. 2026-10-11 06:54 UTCEchelonGraph re-scored
  62. 2026-10-11 06:54 UTCVendor advisory
  63. 2026-10-11 06:54 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  64. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  65. 2026-10-10 18:31 UTCVendor advisory
  66. 2026-10-10 18:31 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  67. 2026-10-10 06:45 UTCEchelonGraph re-scored
  68. 2026-10-10 06:45 UTCVendor advisory
  69. 2026-10-10 06:44 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  70. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  71. 2026-10-09 19:17 UTCVendor advisory
  72. 2026-10-09 19:17 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5
  73. 2026-10-08 23:27 UTCEchelonGraph re-scored
  74. 2026-10-08 23:27 UTCVendor advisory
  75. 2026-10-08 23:27 UTCGHSA enrichmentGHSA-p53f-q495-p25h · GitHub severity HIGH · GitHub CVSS 7.5

Frequently asked(5)

What is CVE-2026-89480?
CVE-2026-89480 is a high-severity vulnerability; its CVE record was published on September 11, 2026. 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:…
When was the CVE record for CVE-2026-89480 published?
The CVE record for CVE-2026-89480 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-89480 actively exploited?
CVE-2026-89480 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89480?
CVE-2026-89480 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89480?
A fix for CVE-2026-89480 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89480 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89480

Explore →

Is Your Infrastructure Affected by CVE-2026-89480?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.