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

> A missing bounds check in the Linux kernel's NVMe over TCP driver allows out-of-bounds memory access, potentially causing crashes or code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-77487, BELL-CVE-2026-23112, DEBIAN-CVE-2026-23112, GHSA-jjrf-jfrm-p64x, ROOT-OS-DEBIAN-11-CVE-2026-23112, ROOT-OS-DEBIAN-12-CVE-2026-23112, ROOT-OS-DEBIAN-13-CVE-2026-23112, ROOT-OS-UBUNTU-2204-CVE-2026-23112, ROOT-OS-UBUNTU-2404-CVE-2026-23112

## What is CVE-2026-23112?

CVE-2026-23112 is a critical memory corruption vulnerability in Linux kernel, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-23112?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-23112?

Apply the vendor's patch.

## Is CVE-2026-23112 being exploited?

There is no known exploitation of CVE-2026-23112 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23112 and fix it if it is affected.

What it is: CVE-2026-23112 is a critical memory corruption vulnerability in Linux kernel, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23112 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23112/ (Markdown: https://insights.sbomify.com/CVE-2026-23112/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23112
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23112
- OSV: https://osv.dev/vulnerability/CVE-2026-23112

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23112/
Summaries are generated and may contain mistakes; the official description above is the record.