GHSA-2VQX-XVHW-M854
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In the Linux kernel, the following vulnerability has been resolved:
RDMA/mlx5: Fix UMR XLT cleanup on ODP populate failure
mlx5r_umr_update_xlt() allocates and DMA maps an XLT buffer with mlx5r_umr_create_xlt(). The buffer is released by the common cleanup path through mlx5r_umr_unmap_free_xlt().
After mlx5_odp_populate_xlt() became fallible, its error path returned directly and skipped that cleanup. This leaks the XLT DMA mapping and buffer. If the emergency XLT page was used, it also leaves xlt_emergency_page_mutex locked.
Break out of the loop so execution falls through the existing cleanup path.
{
"affected": [],
"aliases": [
"CVE-2026-74396"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:41Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/mlx5: Fix UMR XLT cleanup on ODP populate failure\n\nmlx5r_umr_update_xlt() allocates and DMA maps an XLT buffer with\nmlx5r_umr_create_xlt(). The buffer is released by the common cleanup path\nthrough mlx5r_umr_unmap_free_xlt().\n\nAfter mlx5_odp_populate_xlt() became fallible, its error path returned\ndirectly and skipped that cleanup. This leaks the XLT DMA mapping and\nbuffer. If the emergency XLT page was used, it also leaves\nxlt_emergency_page_mutex locked.\n\nBreak out of the loop so execution falls through the existing cleanup path.",
"id": "GHSA-2vqx-xvhw-m854",
"modified": "2026-08-17T06:33:42Z",
"published": "2026-08-15T06:32:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74396"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1eae35b37923cb71b0cb5136d00671440d488b9f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9619909d4869afe720904c6888a289b9ac3055b8"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ffa85a2c197935ace6f1634ad9eb0a44bc615670"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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.
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.