LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23384: RDMA/ionic: Fix kernel stack leak in ionic_create_cq()

In the Linux kernel, the following vulnerability has been resolved: RDMA/ionic: Fix kernel stack leak in ionic_create_cq() struct ionic_cq_resp resp { __u32 cqid[2]; // offset 0 - PARTIALLY SET (see below) __u8 udma_mask; // offset 8 - SET (resp.udma_mask = vcq->udma_mask) __u8 rsvd[7]; // offset 9 - NEVER SET <- LEAK }; rsvd[7]: 7 bytes of stack memory leaked unconditionally. cqid[2]: The loop at line 1256 iterates over udma_idx but skips indices where !(vcq->udma_mask & BIT(udma_idx)). The array has 2 entries but udma_count could be 1, meaning cqid[1] might never be written via ionic_create_cq_common(). If udma_mask only has bit 0 set, cqid[1] (4 bytes) is also leaked. So potentially 11 bytes leaked.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel information disclosure issue in the RDMA/ionic code path. A kernel response structure can return uninitialized stack bytes to a caller. The disclosed amount is small, up to 11 bytes, but kernel memory leaks can assist broader attacks when chained with other weaknesses.

Executive priority

Treat as a focused kernel patching item, not an emergency based on current evidence. Prioritize systems using the affected RDMA/ionic path and include it in routine kernel security maintenance unless vendor guidance raises urgency.

Technical view

ionic_create_cq() builds struct ionic_cq_resp without fully initializing reserved bytes and, in some masks, one cqid entry. The CVE description states 7 bytes leak unconditionally and up to 4 additional bytes may leak, exposing potentially 11 bytes of kernel stack memory.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the RDMA/ionic component reachable. The source bundle lists Linux as affected and references stable kernel fixes, but does not provide a complete operational exposure matrix or distribution-specific package status.

Exploitation context

The bundle does not report active exploitation, public weaponization, or KEV listing. The issue is an information leak rather than direct code execution based on available evidence. Practical impact depends on attacker access to the vulnerable RDMA/ionic path.

Researcher notes

Evidence is narrow but technically specific: uninitialized fields in ionic_cq_resp can leak stack bytes. No CVSS, CWE, exploit status, or distribution package mapping is provided in the bundle, so exposure confirmation needs kernel configuration and vendor backport review.

Mitigation direction

  • Check vendor or distribution advisories for kernels containing the referenced stable fixes.
  • Prioritize updates on systems using RDMA/ionic or related hardware paths.
  • Apply fixed kernel packages when available through normal patch channels.
  • If unused, review vendor guidance before disabling RDMA/ionic functionality.

Validation and detection

  • Inventory Linux kernel versions and RDMA/ionic usage across affected fleets.
  • Confirm whether deployed kernels include one of the referenced stable commits.
  • Review distribution security trackers for backported fixes under CVE-2026-23384.
  • After patching, verify the running kernel matches the remediated package.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23384 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe8521822c733c6deab0f339843cd37cd62c12795, e8521822c733c6deab0f339843cd37cd62c12795, e8521822c733c6deab0f339843cd37cd62c12795unaffected
LinuxLinux6.18, 0, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.