CVE-2026-52908: RDMA: During rereg_mr ensure that REREG_ACCESS is compatible
In the Linux kernel, the following vulnerability has been resolved:
RDMA: During reregmr ensure that REREGACCESS is compatible
If IBMRREREGACCESS changes from RO to RW then the umem has to be re-evaluated to ensure it is properly pinned as RW. Since the umem is hidden inside each driver's mr struct add a ibumemcheckrereg() function that each driver has to call before processing IBMRREREGACCESS.
mlx4 has to retain its duplicate ibaccesswritable check because it implements IBMRREREGACCESS | IBMRREREGTRANS by changing both items in place sequentially while the MR is live, so it will continue to not support this combination.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-52908?
The severity of CVE-2026-52908 is rated as 34, indicating a significant risk associated with the vulnerability.
How do I fix CVE-2026-52908?
To fix CVE-2026-52908, ensure that you apply the latest patches and updates for the Linux kernel that address this vulnerability.
What systems are affected by CVE-2026-52908?
CVE-2026-52908 affects systems running the vulnerable versions of the Linux kernel that utilize RDMA functionalities.
What is the impact of CVE-2026-52908?
The impact of CVE-2026-52908 involves potential unauthorized access due to improper handling of memory regions changing access permissions.
What is the nature of CVE-2026-52908?
CVE-2026-52908 is a vulnerability in the Linux kernel related to RDMA that concerns the compatibility of access permissions during the re-registration of memory regions.