CVE-2026-89482

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone

Commit 25e5cb780e62 ("nvme-tcp: fix possible crash in write_zeroes processing") established that blk_rq_payload_bytes() must not be read without first checking blk_rq_nr_phys_segments(), and recorded the result in nvme_tcp_setup_cmd_pdu() as req->data_len. The receive side was left as it was.

The two differ for REQ_OP_WRITE_ZEROES, which has no physical segments but a non-zero blk_rq_bytes(), so setup leaves req->iter untouched while the receive gate lets a C2HData through and nvme_tcp_recv_data() copies into whatever the previous command on that tag left there. The driver-private area is zeroed only when the tag set is allocated.

Reproduced with a test target that leaves a residual iterator on a tag and then sends a C2HData for a WRITE_ZEROES command on the same tag:

BUG: KASAN: wild-memory-access in _copy_to_iter+0x642/0x1330 Write of size 512 at addr ffe728c2175dfa81 by task kworker/0:1H/103

CPU: 0 UID: 0 PID: 103 Comm: kworker/0:1H Not tainted 7.2.0-rc5-NVMETCP-gf5098b6bae76 #1 PREEMPT(lazy) Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Workqueue: nvme_tcp_wq nvme_tcp_io_work Call Trace: dump_stack_lvl+0x53/0x70 kasan_report+0xce/0x100 ? _copy_to_iter+0x642/0x1330 kasan_check_range+0x105/0x1b0 __asan_memcpy+0x3c/0x60 _copy_to_iter+0x642/0x1330 ? __pfx_sock_has_perm+0x10/0x10 ? worker_thread+0x45b/0xd10 ? __pfx__copy_to_iter+0x10/0x10 ? _raw_spin_lock_bh+0x83/0xe0 ? __pfx__raw_spin_lock_bh+0x10/0x10 __skb_datagram_iter+0xf3/0x820 ? __pfx_simple_copy_to_iter+0x10/0x10 ? __asan_memcpy+0x3c/0x60 ? skb_copy_bits+0x58d/0x830 skb_copy_datagram_iter+0x37/0x120 nvme_tcp_recv_skb+0xa07/0x4320 ? __pfx_nvme_tcp_recv_skb+0x10/0x10 __tcp_read_sock+0x1ab/0x810 ? __pfx_nvme_tcp_recv_skb+0x10/0x10 ? __pfx_lock_sock_nested+0x10/0x10 ? __pfx___tcp_read_sock+0x10/0x10 nvme_tcp_try_recv+0x152/0x1e0 ? __pfx_nvme_tcp_try_recv+0x10/0x10 ? __pfx_mutex_unlock+0x10/0x10 nvme_tcp_io_work+0x1e4/0x6c0 ? __schedule+0x181a/0x49f0 ? __pfx_nvme_tcp_io_work+0x10/0x10 process_one_work+0x633/0x1030

Keep the blk_rq_payload_bytes() test and add req->data_len to it. The old test is what rejects a C2HData naming a tag that is no longer in flight, because blk_update_request() zeroes rq->__data_len on completion; req->data_len and req->curr_bio are driver-private and survive completion, so they cannot stand in for it. Setup initialises the iterator only when both req->curr_bio and req->data_len are set, so the gate now tests the same two.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

September 14, 2026

Advisory Details (8)

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

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dd8906bb8f8d5bf1c9f861e1382c82b87bfe7cab
Web page

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b96e1ff75e5c0ad6e077ac002b1d30b0a2b49528
Web page

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b36161701cb366f416afdcf70771d432a7c74753
Web page

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ed0b61bbc145988be292c4d3ec580aebd8d2bcd
Web page

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a01b58263108eaf9869bb6f82f07709240c6589
Web page

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/641ad3a30ba560f0a9a610376c568d7b75d2a2aa
Web page

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a4aa9e6ad3e35f8e24d5eaf38ee4d437075fb36
Web page

nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32ea8ce96b9bd797c59c351ce490ffd97adaa8c0

Vendor Advisories for CVE-2026-89482(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
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 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 65× in last 7d / 375× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 393 refreshes 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 293 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-89482?
CVE-2026-89482 is a critical-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blkrqpayload_bytes() alone Commit 25e5cb780e62 ("nvme-tcp: fix possible crash in write_zeroes processing") established that blkrqpayload_bytes() must not be read without first checking…
When was the CVE record for CVE-2026-89482 published?
The CVE record for CVE-2026-89482 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 September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-89482 actively exploited?
CVE-2026-89482 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89482?
CVE-2026-89482 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89482?
A fix for CVE-2026-89482 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89482 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-89482

Explore →

Is Your Infrastructure Affected by CVE-2026-89482?

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

Book a Demo →Browse All CVEs