Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 150590d9ab0dbeb0087193058363819d4c82a00f, 372e7318af379eee29ab6e60848ce7d7db76c85a, 5985474e1cb4034680fac2145497a94b0860be50.

Low priority for now. Upgrade to Linux Linux 150590d9ab0dbeb0087193058363819d4c82a00f, 372e7318af379eee29ab6e60848ce7d7db76c85a, 5985474e1cb4034680fac2145497a94b0860be50 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74265

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.13affected
    • ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 372e7318af379eee29ab6e60848ce7d7db76c85aaffected · git
    • ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before c6662f3ad1c7c3549a1c39545651833220b0de89affected · git
    • ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 8e52a247d9aa979d43eb9ff1e445b9b3bf229d4daffected · git
    • ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before a493cbb6b11acd4adc93397a4b12bd460d47620daffected · git
    • ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 62ce489acb428a936bdf243e7b92b3eb341447cfaffected · git
    • ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 150590d9ab0dbeb0087193058363819d4c82a00faffected · git
    • ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f and later · before 5985474e1cb4034680fac2145497a94b0860be50affected · git
    • before 5.13not affected · semver
    • 5.15.212 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72498Aug 15, 2026 · RDMA/bnxt_re: Avoid displaying the kernel pointer
    0Monitor
  • ← EarlierCVE-2026-74263Aug 15, 2026 · net: wwan: t7xx: check skb_clone in control TX
    0Monitor
  • Later →CVE-2026-74266Aug 15, 2026 · net/sched: sch_dualpi2: Do not call qdisc_tree_reduce_backlog during peek before restoring qlen
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux150590d9ab0dbeb0087193058363819d4c82a00fVendor (CNA)
Linux Linux372e7318af379eee29ab6e60848ce7d7db76c85aVendor (CNA)
Linux Linux5985474e1cb4034680fac2145497a94b0860be50Vendor (CNA)
Linux Linux62ce489acb428a936bdf243e7b92b3eb341447cfVendor (CNA)
Linux Linux8e52a247d9aa979d43eb9ff1e445b9b3bf229d4dVendor (CNA)
Linux Linuxa493cbb6b11acd4adc93397a4b12bd460d47620dVendor (CNA)
Linux Linuxc6662f3ad1c7c3549a1c39545651833220b0de89Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records