Answer in brief
CVE-2026-68419 records a Unknown severity vulnerability in RDMA/irdma: Prevent rereg_mr for non-mem regions. 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 <fb46d134e1b8690bed2da9005b36d32d2efd34ac || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <b5029e91c63406e4f4c8d58161048b41b6f0bd8c || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <ca1c29f05274b737dc964e28b97803750d7cf7ec || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <dbaa37e060918c45517786e37ecab0f300b48fa9 || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <a846aecb931b4d65d5eafa92a0623545af46d4f2 || >=6.6.120 <6.6.148 | fb46d134e1b8690bed2da9005b36d32d2efd34ac, b5029e91c63406e4f4c8d58161048b41b6f0bd8c, ca1c29f05274b737dc964e28b97803750d7cf7ec, dbaa37e060918c45517786e37ecab0f300b48fa9, a846aecb931b4d65d5eafa92a0623545af46d4f2, 6.6.148 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
In 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68419 records a Unknown severity vulnerability in RDMA/irdma: Prevent rereg_mr for non-mem regions. 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 <fb46d134e1b8690bed2da9005b36d32d2efd34ac || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <b5029e91c63406e4f4c8d58161048b41b6f0bd8c || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <ca1c29f05274b737dc964e28b97803750d7cf7ec || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <dbaa37e060918c45517786e37ecab0f300b48fa9 || >=5ac388db27c443dadfbb0b8b23fa7ccf429d901a <a846aecb931b4d65d5eafa92a0623545af46d4f2 || >=6.6.120 <6.6.148 | fb46d134e1b8690bed2da9005b36d32d2efd34ac, b5029e91c63406e4f4c8d58161048b41b6f0bd8c, ca1c29f05274b737dc964e28b97803750d7cf7ec, dbaa37e060918c45517786e37ecab0f300b48fa9, a846aecb931b4d65d5eafa92a0623545af46d4f2, 6.6.148 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
In 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.
Quoted source text, attributed separately from HOL analysis.