CVE-2026-74265
Last modified
CVE-2026-74265 is a vulnerability of currently unknown severity. In 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(). EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
In 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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < 372e7318af379eee29ab6e60848ce7d7db76c85a; >= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < c6662f3ad1c7c3549a1c39545651833220b0de89; >= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < 8e52a247d9aa979d43eb9ff1e445b9b3bf229d4d; >= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < a493cbb6b11acd4adc93397a4b12bd460d47620d; >= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < 62ce489acb428a936bdf243e7b92b3eb341447cf; >= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < 150590d9ab0dbeb0087193058363819d4c82a00f; >= ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f, < 5985474e1cb4034680fac2145497a94b0860be50 |
| Linux | Linux | 5.13 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74265?
How severe is CVE-2026-74265?
How do I fix CVE-2026-74265?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-7426Insufficient validation of the prefix length field in IPv6 R…8.1
- CVE-2026-74260In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74261In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74262In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74263In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74264In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74266In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74267In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-74268In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-74269In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-7427GitLab has remediated an issue in GitLab CE/EE affecting all…7.5
- CVE-2026-74270In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-74265?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
