CVE-2026-98479scsi: libiscsi_tcp: Check the data direction of a Data-In PDU
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi_tcp: Check the data direction of a Data-In PDU The Data-In branch of iscsi_tcp_hdr_dissect() resolves the ITT to a task and copies the PDU's data segment into that command's scatterlist without asking whether the command was reading. iscsi_tcp_r2t_rsp() in the same file does ask, and rejects an R2T for a command that is not DMA_TO_DEVICE. A target that answers a WRITE command's ITT with a Data-In therefore has the initiator write target-supplied bytes into the pages that write was about to send. Those are the caller's own pinned pages for an O_DIRECT write, and page cache pages for a buffered one. Observed against a test target that emits one 512-byte Data-In naming a 128 KB write's ITT, after the R2T for that write. With O_DIRECT the caller's buffer ends up holding 512 bytes of the target's data while pwrite() returns 131072. Buffered is quieter: pwrite() and fsync() both succeed, nothing is logged, and reading those blocks back returns the target's bytes out of the page cache without a command going on the wire. Check the direction before using the scatterlist, the way the R2T path already does.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 18, 2026
- First seen by InfoSec Signals
- Oct 18, 2026
Affected products
Linux Linux linux:linux (from the name) | from a081c13e39b5c17052a7b46fafa61019c4c110ff before 79991b770fc3685b1d5cf805b659a879edd19931; from a081c13e39b5c17052a7b46fafa61019c4c110ff before 8db1232945bc663fb94f300090a1fc108de99296; from a081c13e39b5c17052a7b46fafa61019c4c110ff before 94e5bdd08e51c450d954bc592f591c233ca5c9df; from a081c13e39b5c17052a7b46fafa61019c4c110ff before de96dc11aee0d058927bff94a168e3c5c46483e2; from a081c13e39b5c17052a7b46fafa61019c4c110ff before e3b25bf2cf2496e85bc05b33360faf9fdf880e03; from a081c13e39b5c17052a7b46fafa61019c4c110ff before ee56b5e18f566c0b5a183379dcd63d402cebf2f8; from a081c13e39b5c17052a7b46fafa61019c4c110ff before 24ffc919467d20951f0f132d1c75294e2e91e09b; from a081c13e39b5c17052a7b46fafa61019c4c110ff before bce07e2f37b5e4a427d36fd6b1c14067b27591db | CNA record |
References
- https://git.kernel.org/stable/c/79991b770fc3685b1d5cf805b659a879edd19931
- https://git.kernel.org/stable/c/8db1232945bc663fb94f300090a1fc108de99296
- https://git.kernel.org/stable/c/94e5bdd08e51c450d954bc592f591c233ca5c9df
- https://git.kernel.org/stable/c/de96dc11aee0d058927bff94a168e3c5c46483e2
- https://git.kernel.org/stable/c/e3b25bf2cf2496e85bc05b33360faf9fdf880e03
- https://git.kernel.org/stable/c/ee56b5e18f566c0b5a183379dcd63d402cebf2f8
- https://git.kernel.org/stable/c/24ffc919467d20951f0f132d1c75294e2e91e09b
- https://git.kernel.org/stable/c/bce07e2f37b5e4a427d36fd6b1c14067b27591db
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.