GHSA-GRXX-H4MR-VFPG
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In the Linux kernel, the following vulnerability has been resolved:
crypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one
Sashiko notes:
regarding the bounds check in snp_filter_reserved_mem_regions() called via walk_iomem_res_desc(): does the check if ((range_list->num_elements * 16 + 8) > PAGE_SIZE) allow an off-by-one heap buffer overflow?
If range_list->num_elements is 255, 255 * 16 + 8 = 4088, which is <= 4096. Writing range->base (8 bytes) fills 4088-4095, but writing range->page_count (4 bytes) would write to 4096-4099, overflowing the kzalloc-allocated PAGE_SIZE buffer.
Fix this by accounting for the entry about to be written to, in addition to the entries that are already allocated.
{
"affected": [],
"aliases": [
"CVE-2026-74404"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:42Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp - Fix snp_filter_reserved_mem_regions() off-by-one\n\nSashiko notes:\n\n\u003e regarding the bounds check in snp_filter_reserved_mem_regions()\n\u003e called via walk_iomem_res_desc(): does the check\n\u003e if ((range_list-\u003enum_elements * 16 + 8) \u003e PAGE_SIZE)\n\u003e allow an off-by-one heap buffer overflow?\n\u003e\n\u003e If range_list-\u003enum_elements is 255, 255 * 16 + 8 = 4088, which is \u003c= 4096.\n\u003e Writing range-\u003ebase (8 bytes) fills 4088-4095, but writing range-\u003epage_count\n\u003e (4 bytes) would write to 4096-4099, overflowing the kzalloc-allocated\n\u003e PAGE_SIZE buffer.\n\nFix this by accounting for the entry about to be written to, in addition to\nthe entries that are already allocated.",
"id": "GHSA-grxx-h4mr-vfpg",
"modified": "2026-08-17T06:33:43Z",
"published": "2026-08-15T06:32:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74404"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1b864b6cb213bbd7b406e9b2e98c962077f300df"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/830c1f3e71989448652973375ef5e39b6ede47a3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/af7341616b742ad2c374a90998bd650a035f694d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c5c79d92da0f9a09f48be5e2aabed2d6d1a96294"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.