GHSA-M9Q9-JV5W-F7P7
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-24 15:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-98479"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:16:58Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: libiscsi_tcp: Check the data direction of a Data-In PDU\n\nThe Data-In branch of iscsi_tcp_hdr_dissect() resolves the ITT to a task\nand copies the PDU\u0027s data segment into that command\u0027s scatterlist without\nasking whether the command was reading. iscsi_tcp_r2t_rsp() in the same\nfile does ask, and rejects an R2T for a command that is not DMA_TO_DEVICE.\n\nA target that answers a WRITE command\u0027s ITT with a Data-In therefore has\nthe initiator write target-supplied bytes into the pages that write was\nabout to send. Those are the caller\u0027s own pinned pages for an O_DIRECT\nwrite, and page cache pages for a buffered one.\n\nObserved against a test target that emits one 512-byte Data-In naming a 128\nKB write\u0027s ITT, after the R2T for that write. With O_DIRECT the caller\u0027s\nbuffer ends up holding 512 bytes of the target\u0027s data while pwrite()\nreturns 131072. Buffered is quieter: pwrite() and fsync() both succeed,\nnothing is logged, and reading those blocks back returns the target\u0027s bytes\nout of the page cache without a command going on the wire.\n\nCheck the direction before using the scatterlist, the way the R2T path\nalready does.",
"id": "GHSA-m9q9-jv5w-f7p7",
"modified": "2026-10-24T15:32:46Z",
"published": "2026-10-18T18:31:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98479"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/24ffc919467d20951f0f132d1c75294e2e91e09b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/79991b770fc3685b1d5cf805b659a879edd19931"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8db1232945bc663fb94f300090a1fc108de99296"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/94e5bdd08e51c450d954bc592f591c233ca5c9df"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bce07e2f37b5e4a427d36fd6b1c14067b27591db"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/de96dc11aee0d058927bff94a168e3c5c46483e2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e3b25bf2cf2496e85bc05b33360faf9fdf880e03"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ee56b5e18f566c0b5a183379dcd63d402cebf2f8"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.