CVE-2026-68419
Last modified
CVE-2026-68419 is a vulnerability of currently unknown severity. 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..
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 715fdb3b30541cc8180b7cdc6aa9f8c307afdf25, < fb46d134e1b8690bed2da9005b36d32d2efd34ac; >= 5ac388db27c443dadfbb0b8b23fa7ccf429d901a, < b5029e91c63406e4f4c8d58161048b41b6f0bd8c; >= 5ac388db27c443dadfbb0b8b23fa7ccf429d901a, < ca1c29f05274b737dc964e28b97803750d7cf7ec; >= 5ac388db27c443dadfbb0b8b23fa7ccf429d901a, < dbaa37e060918c45517786e37ecab0f300b48fa9; >= 5ac388db27c443dadfbb0b8b23fa7ccf429d901a, < a846aecb931b4d65d5eafa92a0623545af46d4f2; >= 6.6.120, < 6.6.148 |
| Linux | Linux | 6.7 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68419?
How severe is CVE-2026-68419?
How do I fix CVE-2026-68419?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68413In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68414In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68415In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68416In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68417In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68418In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6842A flaw was found in nano. In environments with permissive um…2.5
- CVE-2026-68420In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68421In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68422In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68423In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68424In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68419?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
