# CVE-2026-99154: scsi: libiscsi: Reject a negative task index from parse_pdu_itt


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111290, BELL-CVE-2026-99154, DEBIAN-CVE-2026-99154, GHSA-x6ph-vjqm-9q4f, UBUNTU-CVE-2026-99154

## What is CVE-2026-99154?

CVE-2026-99154 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

scsi: libiscsi: Reject a negative task index from parse_pdu_itt

A transport that implements parse_pdu_itt hands libiscsi an index taken
from the PDU, and both lookups bound it from above only:

      if (i >= session->cmds_max)

i and cmds_max are both int, so a negative index passes and
session->cmds[i] is read from before the array.

be2iscsi produces one. beiscsi_parse_pdu() assigns the raw tag,

      *index = (int)itt;

and beiscsi_complete_pdu() forwards an unsolicited NOP-In from the
hardware async ring without replacing its ITT, so the value is the
target's. It also reports the session's own age rather than the one in
the tag, which leaves the age comparison in iscsi_verify_itt() with
nothing to reject.

Bound the index from below in both lookups.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99154 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99154 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99154 in the wild and no public exploit code.

Affected product: Linux. 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-99154/ (Markdown: https://insights.sbomify.com/CVE-2026-99154/index.md)
```

## Sources

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

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