net: mana: initialize gdma queue id to INVALID_QUEUE_ID
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f · < 150590d9ab0dbeb0087193058363819d4c82a00f| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s mana driver leaves a newly allocated queue ID at zero until firmware assigns an ID. If queue creation fails before then, cleanup can clear the entry for a real completion queue. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the mana driver should check whether their kernel includes the fix; affected versions are not specified.