GHSA-HPRW-93RC-4V5G
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 15:31In the Linux kernel, the following vulnerability has been resolved:
vdpa_sim_blk: reject out-of-range sector starts
vdpasim_blk_check_range() logs an invalid start sector but continues validating the request. The subsequent unsigned capacity subtraction can underflow and let an out-of-range buffer offset reach the data path.
The invalid offset is used by three request paths. VIRTIO_BLK_T_OUT copies guest data to blk->buffer + offset through vringh_iov_pull_iotlb(), causing an out-of-bounds write in _copy_from_iter() or memcpy(). VIRTIO_BLK_T_IN copies from blk->buffer + offset to the guest through vringh_iov_push_iotlb(), causing an out-of-bounds read in _copy_to_iter(). VIRTIO_BLK_T_WRITE_ZEROES passes blk->buffer + offset to memset(), causing an out-of-bounds write.
Reject starts at or beyond the capacity before the subtraction. Treat the capacity boundary as invalid because the IN and OUT paths round byte counts down to sectors for validation but later copy the original byte counts. A sub-sector request at the capacity boundary would otherwise still access past the end of the buffer.
I found this bug myself, though the patch was written with AI assistance.
{
"affected": [],
"aliases": [
"CVE-2026-97991"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:27Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nvdpa_sim_blk: reject out-of-range sector starts\n\nvdpasim_blk_check_range() logs an invalid start sector but continues\nvalidating the request. The subsequent unsigned capacity subtraction can\nunderflow and let an out-of-range buffer offset reach the data path.\n\nThe invalid offset is used by three request paths. VIRTIO_BLK_T_OUT\ncopies guest data to blk-\u003ebuffer + offset through\nvringh_iov_pull_iotlb(), causing an out-of-bounds write in\n_copy_from_iter() or memcpy(). VIRTIO_BLK_T_IN copies from\nblk-\u003ebuffer + offset to the guest through vringh_iov_push_iotlb(),\ncausing an out-of-bounds read in _copy_to_iter().\nVIRTIO_BLK_T_WRITE_ZEROES passes blk-\u003ebuffer + offset to memset(),\ncausing an out-of-bounds write.\n\nReject starts at or beyond the capacity before the subtraction. Treat the\ncapacity boundary as invalid because the IN and OUT paths round byte counts\ndown to sectors for validation but later copy the original byte counts. A\nsub-sector request at the capacity boundary would otherwise still access\npast the end of the buffer.\n\nI found this bug myself, though the patch was written with AI assistance.",
"id": "GHSA-hprw-93rc-4v5g",
"modified": "2026-09-25T15:31:44Z",
"published": "2026-09-25T12:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97991"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0a8693f00c408d85f086ad85d29e7030bf1e2055"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/14acb0d44b7d90a077beb7b92b444b90bafda9d9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a8a1413a2cfdbedc896249f461d6d92efbbfe21f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d6dac17e20fd2abd0eb8c09d69fccf7426e12bcf"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/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.
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.