Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-23112 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Linux Kernel. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation of Remote Services (T1210); ranked at the 40th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-23112 is a high-severity vulnerability in the Linux kernel's nvmet-tcp subsystem, specifically in the nvmet_tcp_build_pdu_iovec() function. This flaw arises from missing bounds checks, allowing the function to iterate beyond the cmd->req.sg scatter-gather array when a PDU length or offset exceeds the sg_cnt. As a result, it accesses invalid sg->length and sg->offset values, which are then passed to _copy_to_iter(), potentially triggering a general protection fault (GPF) or KASAN-detected memory corruption. The issue is classified under CWE-787 (Out-of-bounds Write) with a CVSS v3.1 base score of 9.8.
A remote, unauthenticated attacker (AV:N/AC:L/PR:N/UI:N) can exploit this vulnerability over the network by sending crafted NVMe/TCP PDUs to a Linux system configured as an NVMe target. Successful exploitation leads to high-impact effects on confidentiality, integrity, and availability (C:H/I:H/A:H), including kernel crashes via GPF, memory corruption detectable by KASAN, or potential arbitrary code execution due to the mishandling of bogus scatter-gather entries in the bvec construction.
The referenced stable kernel patches address the issue by adding bounds checks on sg_idx, remaining entries, and sg->length/offset values prior to bvec construction. These fixes are available in the following commits: 043b4307a99f902697349128fde93b2ddde4686c, 1385be357e8acd09b36e026567f3a9d5c61139de, 19672ae68d52ff75347ebe2420dde1b07adca09f, 42afe8ed8ad2de9c19457156244ef3e1eca94b5d, and 52a0a98549344ca20ad81a4176d68d28e3c05a5c. Security practitioners should apply these updates to affected kernel versions hosting nvmet-tcp targets.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6171
Vulnerability Data
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…
more
sg_idx, remaining entries, and sg->length/offset before building the bvec.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.