CVE-2026-23112

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-02-13) is not newer than that change (2026-10-19), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-6171 (ENISA EUVD) · GHSA-jjrf-jfrm-p64x (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec

nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 total (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.5%
EPSS %ILE
40th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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: 3 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 total (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)3 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 total (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

February 13, 2026

Last Modified

October 19, 2026

Advisory Details (8)

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

nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52a0a98549344ca20ad81a4176d68d28e3c05a5c
Web page

nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42afe8ed8ad2de9c19457156244ef3e1eca94b5d
Web page

nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19672ae68d52ff75347ebe2420dde1b07adca09f
Web page

nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1385be357e8acd09b36e026567f3a9d5c61139de
Web page

nvmet-tcp: fix use-before-check of sg in bounds validation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b9981751be14b59b4473383c731c833738aebdb

Vendor Advisories for CVE-2026-23112(1)

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

Patch Availability(21)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1054.60+fips1) @ noble2026-11-02ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1054.60) @ noble2026-11-02ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1111.120~20.04.1) @ focal2026-11-02ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1023.23) @ noble2026-11-02ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1100.98) @ jammy2026-11-02ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1070 (5.15.0-1070.74) @ jammy2026-11-02ubuntu
ubuntuoracle (4.15.0-1129) @ bionic2026-11-02ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1059.65~22.04.1) @ jammy2026-11-02ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1106.115~20.04.1) @ focal2026-11-02ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.177.187~20.04.1) @ focal2026-11-02ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1052.55~22.04.1) @ jammy2026-11-02ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1143.174) @ focal2026-11-02ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1014.14) @ questing2026-11-02ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-11-02ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1104.110~20.04.1) @ focal2026-11-02ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1076 (5.4.0-1076.80) @ focal2026-11-02ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-23.23) @ questing2026-11-02ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1013.13) @ questing2026-11-02ubuntu
ubuntulinux-virtual-6.8 (6.8.0-111.111) @ noble2026-11-02ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-11-02ubuntu
linuxKernel @ 5.10.253 (fixes >=5.0.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (49 versions)
  • every version up to 5.10.251-1: fixed in 5.10.251-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.162-1~deb11u1 (15 versions)
  • every version up to 6.1.164-1~deb11u1: fixed in 6.1.164-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)
  • every version up to 6.1.164-1: fixed in 6.1.164-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.73-1~bpo12+1 (12 versions)
  • every version up to 6.12.73-1: fixed in 6.12.73-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (100 versions)
  • every version up to 6.18.10-1: fixed in 6.18.10-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 25× in last 7d / 93× 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 325 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 225 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-23112?
CVE-2026-23112 is a critical-severity vulnerability; its CVE record was published on February 13, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter()…
When was the CVE record for CVE-2026-23112 published?
The CVE record for CVE-2026-23112 was published on February 13, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-23112 actively exploited?
CVE-2026-23112 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23112?
CVE-2026-23112 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-23112?
A fix for CVE-2026-23112 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23112 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-23112

Explore →

Is Your Infrastructure Affected by CVE-2026-23112?

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