Answer in brief
CVE-2026-43120 records a Unknown severity vulnerability in RDMA/irdma: Fix double free related to rereg_user_mr. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=715fdb3b30541cc8180b7cdc6aa9f8c307afdf25 <62298a48f8b8788ad8b8464e6ffdf1ddebd2217e || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <66964118f1f50ed85001c8fc9f7ab5bbdd021ee0 || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <0f22c32141acdcda266b26cab2b830baf870f3e0 || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <0c5d70bcb9d2275a1c8515a924016fcfeb4ab441 || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <29a3edd7004bb635d299fb9bc6f0ea4ef13ed5a2 || >=6.6.120 <6.6.136 | 62298a48f8b8788ad8b8464e6ffdf1ddebd2217e, 66964118f1f50ed85001c8fc9f7ab5bbdd021ee0, 0f22c32141acdcda266b26cab2b830baf870f3e0, 0c5d70bcb9d2275a1c8515a924016fcfeb4ab441, 29a3edd7004bb635d299fb9bc6f0ea4ef13ed5a2, 6.6.136 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix double free related to rereg_user_mr If IB_MR_REREG_TRANS is set during rereg_user_mr, the umem will be released and a new one will be allocated in irdma_rereg_mr_trans. If any step of irdma_rereg_mr_trans fails after the new umem is allocated, it releases the umem, but does not set iwmr->region to NULL. The problem is that this failure is propagated to the user, who will then call ibv_dereg_mr (as they should). Then, the dereg_mr path will see a non-NULL umem and attempt to call ib_umem_release again. Fix this by setting iwmr->region to NULL after ib_umem_release. Fixed: 5ac388db27c4 ("RDMA/irdma: Add support to re-register a memory region")
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-43120 records a Unknown severity vulnerability in RDMA/irdma: Fix double free related to rereg_user_mr. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=715fdb3b30541cc8180b7cdc6aa9f8c307afdf25 <62298a48f8b8788ad8b8464e6ffdf1ddebd2217e || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <66964118f1f50ed85001c8fc9f7ab5bbdd021ee0 || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <0f22c32141acdcda266b26cab2b830baf870f3e0 || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <0c5d70bcb9d2275a1c8515a924016fcfeb4ab441 || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <29a3edd7004bb635d299fb9bc6f0ea4ef13ed5a2 || >=6.6.120 <6.6.136 | 62298a48f8b8788ad8b8464e6ffdf1ddebd2217e, 66964118f1f50ed85001c8fc9f7ab5bbdd021ee0, 0f22c32141acdcda266b26cab2b830baf870f3e0, 0c5d70bcb9d2275a1c8515a924016fcfeb4ab441, 29a3edd7004bb635d299fb9bc6f0ea4ef13ed5a2, 6.6.136 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix double free related to rereg_user_mr If IB_MR_REREG_TRANS is set during rereg_user_mr, the umem will be released and a new one will be allocated in irdma_rereg_mr_trans. If any step of irdma_rereg_mr_trans fails after the new umem is allocated, it releases the umem, but does not set iwmr->region to NULL. The problem is that this failure is propagated to the user, who will then call ibv_dereg_mr (as they should). Then, the dereg_mr path will see a non-NULL umem and attempt to call ib_umem_release again. Fix this by setting iwmr->region to NULL after ib_umem_release. Fixed: 5ac388db27c4 ("RDMA/irdma: Add support to re-register a memory region")
Quoted source text, attributed separately from HOL analysis.