CVE-2026-98479: Linux kernel · scsi: libiscsi_tcp: Check the data direction of a Data-In PDU
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in ee56b5e18f566c0b5a183379dcd63d402cebf2f8 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ee56b5e18f566c0b5a183379dcd63d402cebf2f8, e3b25bf2cf2496e85bc05b33360faf9fdf880e03, de96dc11aee0d058927bff94a168e3c5c46483e2 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix for this vulnerability is available and has been applied in the Linux kernel commits identified by the fixedVersions hashes. Users and administrators should update affected Linux kernel versions to a fixed release containing these patches. No additional mitigation is required once the kernel is updated.
Description
CVE-2026-98479 is a vulnerability in the Linux kernel's libiscsi_tcp component where the data direction of a Data-In PDU is not properly checked. This flaw allows a target to cause the initiator to write target-supplied data into the initiator's own memory pages during a WRITE command, potentially leading to data corruption. The issue affects Linux kernel version 2.6.29 and has been fixed in subsequent commits.
References
- git.kernel.org/stable/c/79991b770fc3685b1d5cf805b659a879edd19931 (opens in a new tab)
- git.kernel.org/stable/c/8db1232945bc663fb94f300090a1fc108de99296 (opens in a new tab)
- git.kernel.org/stable/c/94e5bdd08e51c450d954bc592f591c233ca5c9df (opens in a new tab)
- git.kernel.org/stable/c/de96dc11aee0d058927bff94a168e3c5c46483e2 (opens in a new tab)
- git.kernel.org/stable/c/e3b25bf2cf2496e85bc05b33360faf9fdf880e03 (opens in a new tab)
- git.kernel.org/stable/c/ee56b5e18f566c0b5a183379dcd63d402cebf2f8 (opens in a new tab)
- git.kernel.org/stable/c/24ffc919467d20951f0f132d1c75294e2e91e09b (opens in a new tab)
- git.kernel.org/stable/c/bce07e2f37b5e4a427d36fd6b1c14067b27591db (opens in a new tab)