GHSA-F527-F42M-RC5Q
Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-14 00:31In the Linux kernel, the following vulnerability has been resolved:
RDMA/irdma: Prevent rereg_mr for non-mem regions
When a QP/CQ/SRQ is created, a two step process is used where the buffer is allocated in userspace and explicitly registered with the normal reg_mr mechanism prior to creating the actual QP/CQ/SRQ object.
These special registrations are indicated via an ABI field so the driver knows that they do not have a valid mkey and to skip the actual CQP command submission.
Since these are real MR objects from the core's perspective, it is possible for a user application to invoke rereg_mr on them and cause a real CQP op to be emitted with the zero-initialized mkey value of 0.
Fix this by preventing rereg_mr on these special regions.
{
"affected": [],
"aliases": [
"CVE-2026-68419"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-10T13:20:35Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/irdma: Prevent rereg_mr for non-mem regions\n\nWhen a QP/CQ/SRQ is created, a two step process is used\nwhere the buffer is allocated in userspace and explicitly\nregistered with the normal reg_mr mechanism prior to creating\nthe actual QP/CQ/SRQ object.\n\nThese special registrations are indicated via an ABI field\nso the driver knows that they do not have a valid mkey and\nto skip the actual CQP command submission.\n\nSince these are real MR objects from the core\u0027s perspective,\nit is possible for a user application to invoke rereg_mr on them\nand cause a real CQP op to be emitted with the zero-initialized\nmkey value of 0.\n\nFix this by preventing rereg_mr on these special regions.",
"id": "GHSA-f527-f42m-rc5q",
"modified": "2026-08-14T00:31:58Z",
"published": "2026-08-10T15:33:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68419"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a846aecb931b4d65d5eafa92a0623545af46d4f2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b5029e91c63406e4f4c8d58161048b41b6f0bd8c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ca1c29f05274b737dc964e28b97803750d7cf7ec"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dbaa37e060918c45517786e37ecab0f300b48fa9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fb46d134e1b8690bed2da9005b36d32d2efd34ac"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.