GHSA-69MF-3X6R-XPP9
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
drm/xe: free madvise VMA array on L2 flush failure
xe_vm_madvise_ioctl() allocates madvise_range.vmas in get_vmas(). After get_vmas() succeeds with at least one VMA, error paths must go through free_vmas so the array is released before the madvise details are destroyed.
The L2 flush validation path added for PAT madvise rejects some SVM/userptr ranges after get_vmas() has succeeded, but jumps directly to madv_fini. This skips kfree(madvise_range.vmas), leaking the VMA array on each failed ioctl.
Jump to free_vmas instead, matching the other validation failure paths after get_vmas() has succeeded.
(cherry picked from commit c3a1c3579b1250060da73507a4acef712974c78a)
{
"affected": [],
"aliases": [
"CVE-2026-72311"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:03Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe: free madvise VMA array on L2 flush failure\n\nxe_vm_madvise_ioctl() allocates madvise_range.vmas in get_vmas().\nAfter get_vmas() succeeds with at least one VMA, error paths must go\nthrough free_vmas so the array is released before the madvise details are\ndestroyed.\n\nThe L2 flush validation path added for PAT madvise rejects some\nSVM/userptr ranges after get_vmas() has succeeded, but jumps directly to\nmadv_fini. This skips kfree(madvise_range.vmas), leaking the VMA array on\neach failed ioctl.\n\nJump to free_vmas instead, matching the other validation failure paths\nafter get_vmas() has succeeded.\n\n(cherry picked from commit c3a1c3579b1250060da73507a4acef712974c78a)",
"id": "GHSA-69mf-3x6r-xpp9",
"modified": "2026-08-15T06:32:20Z",
"published": "2026-08-15T06:32:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72311"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/14abbed336a2d1bbd726c25d148d2ec0ff928073"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bf126747e7bff55e5ba0b1ec10fc5fce99feaed9"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.