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

GHSA-J69G-MRR3-P2QH

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/core: Fix FRMR aging push to queue error flow

Aging pools with pinned handles requires moving handles from the active queue to a non-empty inactive queue that might fail on new page allocation, we are currently not handling the fault and leaking any mkey that fails the push.

Fix by Introducing push_queue_to_queue_locked() that fills the destination's partial tail page from the source and then splices the remaining source pages onto the destination, performing no allocation.

Replace the per-handle move loop in age_pinned_pool() and the open-coded splice in pool_aging_work() with calls to the helper. As the helper cannot fail under memory pressure, removing a class of GFP_ATOMIC allocations under the pool lock and simplifying the error flow.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-74299"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:29Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Fix FRMR aging push to queue error flow\n\nAging pools with pinned handles requires moving handles from the\nactive queue to a non-empty inactive queue that might fail on new page\nallocation, we are currently not handling the fault and leaking any mkey\nthat fails the push.\n\nFix by Introducing push_queue_to_queue_locked() that fills the\ndestination\u0027s partial tail page from the source and then splices the\nremaining source pages onto the destination, performing no allocation.\n\nReplace the per-handle move loop in age_pinned_pool() and the\nopen-coded splice in pool_aging_work() with calls to the helper.\nAs the helper cannot fail under memory pressure, removing a class of\nGFP_ATOMIC allocations under the pool lock and simplifying the error\nflow.",
  "id": "GHSA-j69g-mrr3-p2qh",
  "modified": "2026-08-15T06:32:28Z",
  "published": "2026-08-15T06:32:28Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74299"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c6936506ed556ce3ccad36ab999baf2764dd7d25"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/edf133d28fc43f7f8b0da43a8d5b93fdf8073d35"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…