CVE-2026-74265

net: mana: initialize gdma queue id to INVALID_QUEUE_ID

N/A
Published: August 15, 2026 at 05:57 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.13 ≤ v < 5.15.2125.13 ≤ v < 6.1.1785.13 ≤ v < 6.12.975.13 ≤ v < 6.18.405.13 ≤ v < 6.6.1455.13 ≤ v < 7.1.55.13 ≤ v < 7.25.13ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f
Vendor states this is fixed in 150590d9ab0dbeb0087193058363819d4c82a00f (fixed)
Vendor states this is fixed in 372e7318af379eee29ab6e60848ce7d7db76c85a (fixed)
Vendor states this is fixed in 5985474e1cb4034680fac2145497a94b0860be50 (fixed)
Vendor states this is fixed in 62ce489acb428a936bdf243e7b92b3eb341447cf (fixed)
Vendor states this is fixed in 8e52a247d9aa979d43eb9ff1e445b9b3bf229d4d (fixed)
Vendor states this is fixed in a493cbb6b11acd4adc93397a4b12bd460d47620d (fixed)
Vendor states this is fixed in c6662f3ad1c7c3549a1c39545651833220b0de89 (fixed)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card