GHSA-3QW4-V9V4-3WW5
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
net: mana: initialize gdma queue id to INVALID_QUEUE_ID
mana_gd_create_mana_wq_cq() leaves queue->id as 0 (from kzalloc_obj()) until mana_create_wq_obj() assigns the firmware-returned id. If creation fails before that, cleanup calls mana_gd_destroy_cq() with id 0, NULLing gc->cq_table[0] and silently breaking whichever real CQ owns that slot.
Initialize queue->id to INVALID_QUEUE_ID right after allocation, matching mana_gd_create_eq(). The existing (id >= max_num_cqs) guard then short-circuits cleanly.
{
"affected": [],
"aliases": [
"CVE-2026-74265"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:25Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: mana: initialize gdma queue id to INVALID_QUEUE_ID\n\nmana_gd_create_mana_wq_cq() leaves queue-\u003eid as 0 (from kzalloc_obj())\nuntil mana_create_wq_obj() assigns the firmware-returned id. If creation\nfails before that, cleanup calls mana_gd_destroy_cq() with id 0, NULLing\ngc-\u003ecq_table[0] and silently breaking whichever real CQ owns that slot.\n\nInitialize queue-\u003eid to INVALID_QUEUE_ID right after allocation, matching\nmana_gd_create_eq(). The existing (id \u003e= max_num_cqs) guard then\nshort-circuits cleanly.",
"id": "GHSA-3qw4-v9v4-3ww5",
"modified": "2026-08-15T06:32:27Z",
"published": "2026-08-15T06:32:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74265"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/150590d9ab0dbeb0087193058363819d4c82a00f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/372e7318af379eee29ab6e60848ce7d7db76c85a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5985474e1cb4034680fac2145497a94b0860be50"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/62ce489acb428a936bdf243e7b92b3eb341447cf"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8e52a247d9aa979d43eb9ff1e445b9b3bf229d4d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a493cbb6b11acd4adc93397a4b12bd460d47620d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c6662f3ad1c7c3549a1c39545651833220b0de89"
}
],
"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.