Menu

Star on GitHub · 3.4k

CVE-2026-98366

7.8 · HIGH

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: validate access flags before swapping the MR's PD rxe_rereg_user_mr() reassigns mr->ibmr.pd first and only then valid…

Published Oct 6, 2026EPSS 0.12%

Overview

CVE-2026-98366 is a high-severity vulnerability. It was published on October 6, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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

RDMA/rxe: validate access flags before swapping the MR's PD

rxe_rereg_user_mr() reassigns mr->ibmr.pd first and only then

validates the IB_MR_REREG_ACCESS argument:

if (flags & IB_MR_REREG_PD) {

rxe_put(old_pd);

rxe_get(pd);

mr->ibmr.pd = ibpd;

}

if (flags & IB_MR_REREG_ACCESS) {

if (access & ~RXE_ACCESS_SUPPORTED_MR)

return ERR_PTR(-EOPNOTSUPP);

mr->access = access;

}

Both flags pass the entry check because RXE_MR_REREG_SUPPORTED is

IB_MR_REREG_PD | IB_MR_REREG_ACCESS, so a caller can reach the access

check with mr->ibmr.pd already reassigned.

mr->ibmr.pd is owned by the core, which adjusts pd->usecnt only on the

success path: ib_uverbs_rereg_mr() jumps to put_new_uobj on a driver error

without undoing the reassignment, so mr->pd == new_pd while the usecnts

still charge the MR to orig_pd. ib_dereg_mr_user() then decrements

new_pd, whose count can reach zero while a memory window still references

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-98366?

CVE-2026-98366 is a high-severity vulnerability. It was published on October 6, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-98366?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-98366?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-98366?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-98366 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
LiveWatch live →