GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-R8XX-CVRR-FWJ4

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

RDMA/irdma: Fix OOB read during CQ MR registration

Sashiko pointed out an unrelated bug during a previous patch: https://sashiko.dev/#/patchset/20260512183852.614045-1-jmoroni%40google.com

This change fixes the bug by eliminating the cqmr->split field which was not being set properly and instead just checks the CQ resize feature flag directly.

The cqmr->split field essentially tracks whether IRDMA_FEATURE_CQ_RESIZE is set, but it was not being set until CQ creation time, which is after CQ memory registration (the only other place where it is referenced).

As a result, it would always be false during MR registration and would therefore cause irdma_handle_q_mem to populate cqmr->shadow even for GEN_2 HW and beyond:

cqmr->shadow = (dma_addr_t)arr[req->cq_pages];

The issue is that for GEN_2 and beyond, req->cq_pages may be exactly equal to iwmr->page_cnt and therefore equal to the size of arr, which would cause an OOB read by one.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-74346"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:35Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/irdma: Fix OOB read during CQ MR registration\n\nSashiko pointed out an unrelated bug during a previous patch:\nhttps://sashiko.dev/#/patchset/20260512183852.614045-1-jmoroni%40google.com\n\nThis change fixes the bug by eliminating the cqmr-\u003esplit field which\nwas not being set properly and instead just checks the CQ resize\nfeature flag directly.\n\nThe cqmr-\u003esplit field essentially tracks whether IRDMA_FEATURE_CQ_RESIZE\nis set, but it was not being set until CQ creation time, which is _after_\nCQ memory registration (the only other place where it is referenced).\n\nAs a result, it would always be false during MR registration and would\ntherefore cause irdma_handle_q_mem to populate cqmr-\u003eshadow even for GEN_2\nHW and beyond:\n\n    cqmr-\u003eshadow = (dma_addr_t)arr[req-\u003ecq_pages];\n\nThe issue is that for GEN_2 and beyond, req-\u003ecq_pages may be exactly equal\nto iwmr-\u003epage_cnt and therefore equal to the size of arr, which would cause\nan OOB read by one.",
  "id": "GHSA-r8xx-cvrr-fwj4",
  "modified": "2026-08-15T06:32:30Z",
  "published": "2026-08-15T06:32:30Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74346"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3159c6fac43dc24b34d31971884d98a7a1bf4c4b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4385ddd654d90245eeb83b3cb539670ab5c85ba4"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/54cab78df0375196aaec4e3109191653d21751df"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a80b3b13786e9ab1c52b31a1f16c7d6708fa9220"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ad360a31092a870633ec255b96f50181628b4de0"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d566002de555b18cc395012c5c1cb8682fc6d2a9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d5aa82da8f65562da996d184686db9d0ea718b91"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.