LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical Linux kernel flaw in the NVMe over TCP target path. A remote, unauthenticated peer may trigger unsafe memory handling when the service processes crafted PDU lengths or offsets. Business risk is highest for systems exposing NVMe/TCP storage services.

Executive priority

Treat as urgent for exposed storage infrastructure. Prioritize internet-facing or broadly reachable NVMe/TCP targets first, then embedded appliances and vendor-managed platforms. Systems without nvmet-tcp enabled have lower practical exposure but still need inventory confirmation.

Technical view

nvmet_tcp_build_pdu_iovec() could walk beyond cmd->req.sg when PDU length or offset exceeds sg_cnt, then use invalid scatter-gather length or offset values. The kernel fix adds bounds checks before building the bvec. CVSS is 9.8 with network, low-complexity, unauthenticated attack characteristics.

Likely exposure

Exposure is likely limited to Linux systems running the NVMe target over TCP component. Storage targets, appliances, and products embedding affected Linux kernels need mapping against vendor kernels and backports. The provided evidence does not identify every affected distribution or Siemens product model.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. The CVSS vector indicates remote unauthenticated reachability if nvmet-tcp is exposed, but no public exploit status is established by the provided sources.

Researcher notes

Evidence supports an out-of-bounds scatter-gather handling bug in Linux nvmet-tcp fixed by stable kernel commits. The affected version data is broad and commit-oriented, so distribution-specific fixed versions require vendor advisory confirmation. Do not assume active exploitation from severity alone.

Mitigation direction

  • Apply Linux stable or vendor kernel updates containing the referenced nvmet-tcp bounds-check fixes.
  • Check distribution and appliance advisories for backported fixes matching your kernel build.
  • Disable nvmet-tcp where NVMe/TCP target functionality is not required.
  • Restrict NVMe/TCP access to trusted storage networks and management segments.
  • Review the Siemens advisory if Siemens products are in scope.

Validation and detection

  • Inventory hosts with the nvmet-tcp target module or NVMe/TCP target services enabled.
  • Map running kernel versions to vendor advisories and the referenced stable commits.
  • Confirm NVMe/TCP listener exposure from network and firewall policy records.
  • Verify patched kernels are active after reboot, not only installed.
  • Check logs for kernel GPF, KASAN, or nvmet-tcp crash indicators.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23112 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-23112Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux872d26a391da92ed8f0c0f5cb5fef428067b7f30, 872d26a391da92ed8f0c0f5cb5fef428067b7f30, 872d26a391da92ed8f0c0f5cb5fef428067b7f30, 872d26a391da92ed8f0c0f5cb5fef428067b7f30, 872d26a391da92ed8f0c0f5cb5fef428067b7f30, 872d26a391da92ed8f0c0f5cb5fef428067b7f30, 872d26a391da92ed8f0c0f5cb5fef428067b7f30unaffected
LinuxLinux5.0, 0, 5.10.253, 5.15.200, 6.1.163, 6.6.124, 6.12.70, 6.18.10, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.