VulnerabilityPublished 28 Oct 2026

CVE-2026-99154: Linux kernel · scsi: libiscsi: Reject a negative task index from parse_pdu_itt

Source GCVE Database

Authoritative record:CVE-2026-99154

Not known to be exploited · fixed in 35b60549a956237488c89a2d85352e026e7d55b7 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 13:58 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in 35b60549a956237488c89a2d85352e026e7d55b7, 8ee2a09a1dbb257c9e828ad2497f8e4832dfb142, 6cadfa6f1f5896632d4223d3b7addb2a29fea74e

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-x6ph-vjqm-9q4f

What to do

Upgrade Linux kernel to 35b60549a956237488c89a2d85352e026e7d55b7, 8ee2a09a1dbb257c9e828ad2497f8e4832dfb142 or 6cadfa6f1f5896632d4223d3b7addb2a29fea74e.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bfead3b2cb4607c71831423c3ee97d22cd0c9dcb, < 35b60549a956237488c89a2d85352e026e7d55b7	Fixed in 35b60549a956237488c89a2d85352e026e7d55b7
LinuxLinux	Affected ≥ bfead3b2cb4607c71831423c3ee97d22cd0c9dcb, < 8ee2a09a1dbb257c9e828ad2497f8e4832dfb142	Fixed in 8ee2a09a1dbb257c9e828ad2497f8e4832dfb142
LinuxLinux	Affected ≥ bfead3b2cb4607c71831423c3ee97d22cd0c9dcb, < 6cadfa6f1f5896632d4223d3b7addb2a29fea74e	Fixed in 6cadfa6f1f5896632d4223d3b7addb2a29fea74e
LinuxLinux	Affected =2.6.33	Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel to add a lower bound check on the task index in parse_pdu_itt, preventing negative index values from causing out-of-bounds access. Users should apply the official kernel updates that include this patch once available. No other mitigation actions are indicated.

Description

A vulnerability in the Linux kernel's libiscsi SCSI subsystem allows a negative task index to be used in parse_pdu_itt, leading to out-of-bounds array access. This occurs because the index is only checked for an upper bound but not for a lower bound, allowing negative values to access memory before the array. The issue arises specifically with beiscsi transport handling unsolicited NOP-In PDUs with unvalidated ITT values. The flaw has been resolved by adding a lower bound check on the index.

References

Community reviews

Loading reviews…