# nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec

CVE record · `CVE-2026-23112`

- **Identifiers:** `CVE-2026-23112`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** Linux
- **Weakness (CWE):** [CWE-125](https://cwe.mitre.org/data/definitions/125.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 13 Feb 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 13 Feb 2026, 13:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 0b9981751be14b59b4473383c731c833738aebdb` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 42afe8ed8ad2de9c19457156244ef3e1eca94b5d` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 1385be357e8acd09b36e026567f3a9d5c61139de` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before dca1a6ba0da9f472ef040525fab10fd9956db59f` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 19672ae68d52ff75347ebe2420dde1b07adca09f` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before ab200d71553bdcf4de554a5985b05b2dd606bc57` (git)
  - affected: `872d26a391da92ed8f0c0f5cb5fef428067b7f30 to before 52a0a98549344ca20ad81a4176d68d28e3c05a5c` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.0`
  - unaffected: `before 5.0` (semver)
  - unaffected: `5.10.253 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.200 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.163 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.124 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.70 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.10 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0048, the 41st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 13 Feb 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-23112](https://www.cve.org/CVERecord?id=CVE-2026-23112)
- [NVD: CVE-2026-23112](https://nvd.nist.gov/vuln/detail/CVE-2026-23112)

### References from the CNA

- <https://git.kernel.org/stable/c/0b9981751be14b59b4473383c731c833738aebdb>
- <https://git.kernel.org/stable/c/42afe8ed8ad2de9c19457156244ef3e1eca94b5d>
- <https://git.kernel.org/stable/c/1385be357e8acd09b36e026567f3a9d5c61139de>
- <https://git.kernel.org/stable/c/dca1a6ba0da9f472ef040525fab10fd9956db59f>
- <https://git.kernel.org/stable/c/19672ae68d52ff75347ebe2420dde1b07adca09f>
- <https://git.kernel.org/stable/c/ab200d71553bdcf4de554a5985b05b2dd606bc57>
- <https://git.kernel.org/stable/c/52a0a98549344ca20ad81a4176d68d28e3c05a5c>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-23112>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-23112/>. Everything for agents: <https://agentprime.io/llms.txt>.
