CVE-2026-23112

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

February 13, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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(18)

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 rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (49 versions)5.10.251-1
linux-6.16.1.106-3~deb11u1 ... 6.1.162-1~deb11u1 (15 versions)6.1.164-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.73-1~bpo12+1 (12 versions)6.12.73-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)6.18.10-1

Weakness Classification(1)

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

All Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 224 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23112?
CVE-2026-23112 is a critical vulnerability published on February 13, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmettcpbuildpduiovec nvmettcpbuildpduiovec() 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 copytoiter() GPF/KASAN.…
When was CVE-2026-23112 disclosed?
CVE-2026-23112 was first published in the National Vulnerability Database on February 13, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23112 actively exploited?
CVE-2026-23112 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.6% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23112, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.