Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74265net: mana: initialize gdma queue id to INVALID_QUEUE_ID

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f – < 372e7318af379eee29ab6e60848ce7d7db76c85a
    • affected ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f – < c6662f3ad1c7c3549a1c39545651833220b0de89
    • affected ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f – < 8e52a247d9aa979d43eb9ff1e445b9b3bf229d4d
    • affected ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f – < a493cbb6b11acd4adc93397a4b12bd460d47620d
    • affected ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f – < 62ce489acb428a936bdf243e7b92b3eb341447cf
    • affected ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f – < 150590d9ab0dbeb0087193058363819d4c82a00f
    • affected ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f – < 5985474e1cb4034680fac2145497a94b0860be50
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74265 badge
[![CVE-2026-74265](https://cveledger.app/badge/CVE-2026-74265.svg)](https://cveledger.app/cve/CVE-2026-74265)

Record last updated .