The bug causes the RDMA umem subsystem to unpin a DMA buffer twice when a mapping failure occurs. The first unpin is performed immediately on failure but the internal pinned flag remains set. When the buffer is released later, a second unpin is attempted, which may disrupt kernel memory management and lead to kernel instability. The description does not mention a crash or data corruption, so while the precise impact is uncertain, the double unpin could result in improper resource cleanup.

All Linux kernels that include the RDMA umem code path prior to the series of commits that address the double‑unpin condition are potentially affected. Versions older than the patched revisions (identified by the provided commit hashes) are at risk. No explicit version range is listed, so any system running a pre‑patched kernel should consider this issue.

The CVSS score of 7.8 indicates high severity, while the EPSS score is below 1%, suggesting a very low probability of exploitation. Because the double‑unpin occurs only when the RDMA umem mapping fails, an attacker would need to trigger that failure, implying a local or privileged context. Based on the description, it is inferred that the attack vector is likely local or requires elevated privileges; no remote execution is indicated. The vulnerability is not listed in the CISA KEV catalog, meaning no known active exploitation exists.