GHSA-MM4R-FCQ9-PFR4
Vulnerability from github – Published: 2026-10-13 18:30 – Updated: 2026-10-13 18:30XSA-501 was about issues with v1 -> v2 and v2 -> v1 changes racing certain other grant table operations. Sadly a v2 -> v1 -> v2 change has yet another effect which wasn't accounted for: During the first change, status pages would be freed. During the second change they would be allocated again. Hence across the full pair of change the addresses of the status pages may change, rendering stale previously calculated pointers into the status array.
{
"affected": [],
"aliases": [
"CVE-2026-79610"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-13T16:17:23Z",
"severity": null
},
"details": "XSA-501 was about issues with v1 -\u003e v2 and v2 -\u003e v1 changes racing certain\nother grant table operations. Sadly a v2 -\u003e v1 -\u003e v2 change has yet\nanother effect which wasn\u0027t accounted for: During the first change, status\npages would be freed. During the second change they would be allocated\nagain. Hence across the full pair of change the addresses of the status\npages may change, rendering stale previously calculated pointers into the\nstatus array.",
"id": "GHSA-mm4r-fcq9-pfr4",
"modified": "2026-10-13T18:30:52Z",
"published": "2026-10-13T18:30:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-79610"
},
{
"type": "WEB",
"url": "https://xenbits.xenproject.org/xsa/advisory-517.html"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2026/10/13/6"
},
{
"type": "WEB",
"url": "http://xenbits.xen.org/xsa/advisory-517.html"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
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.