GHSA-J7PF-235F-JCQV
Vulnerability from github – Published: 2026-08-22 18:30 – Updated: 2026-08-25 06:31In the Linux kernel, the following vulnerability has been resolved:
vhost-scsi: Validate T10 PI scatterlist counts
When T10 PI is negotiated, vhost-scsi splits protection bytes from the data iterator before mapping the request scatterlists. A malformed request can claim protection bytes that cover or exceed the full payload length. The former leaves no data bytes to map, while the latter underflows exp_data_len before advancing the iterator. Both cases can let a zero data SGL count reach sg_alloc_table_chained(), which triggers BUG_ON(!nents).
Reject protection lengths that cover or exceed the payload before subtracting prot_bytes and advancing the iterator. Also propagate negative errors from the protection SGL calculation before calling the allocator, matching the data SGL path.
{
"affected": [],
"aliases": [
"CVE-2026-74703"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-22T16:16:44Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nvhost-scsi: Validate T10 PI scatterlist counts\n\nWhen T10 PI is negotiated, vhost-scsi splits protection bytes from\nthe data iterator before mapping the request scatterlists. A malformed\nrequest can claim protection bytes that cover or exceed the full payload\nlength. The former leaves no data bytes to map, while the latter\nunderflows exp_data_len before advancing the iterator. Both cases can let\na zero data SGL count reach sg_alloc_table_chained(), which triggers\nBUG_ON(!nents).\n\nReject protection lengths that cover or exceed the payload before\nsubtracting prot_bytes and advancing the iterator. Also propagate\nnegative errors from the protection SGL calculation before calling the\nallocator, matching the data SGL path.",
"id": "GHSA-j7pf-235f-jcqv",
"modified": "2026-08-25T06:31:28Z",
"published": "2026-08-22T18:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74703"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2417a498cf3fe64d06faf87e236eda98dd4f04e0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d876c493fc4b811941bfeb4c80beb2dfc4bf025e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f8fe3f8d342da750dd10361bf66009fd3072926b"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H",
"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.