CyberSecBulletin
CVE-2026-68419NVD status: Received

In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Prevent…

Published Updated By the CyberSecBulletin desk

CVE-2026-68419 is a high-severity improper input validation vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions fb46d134e1b8690bed2da9005b36d32d2efd34ac, b5029e91c63406e4f4c8d58161048b41b6f0bd8c, ca1c29f05274b737dc964e28b97803750d7cf7ec as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to fb46d134e1b8690bed2da9005b36d32d2efd34ac or b5029e91c63406e4f4c8d58161048b41b6f0bd8c or ca1c29f05274b737dc964e28b97803750d7cf7ec or dbaa37e060918c45517786e37ecab0f300b48fa9, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux715fdb3b30541cc8180b7cdc6aa9f8c307afdf25 up to, but not including, fb46d134e1b8690bed2da9005b36d32d2efd34ac; 5ac388db27c443dadfbb0b8b23fa7ccf429d901a up to, but not including, b5029e91c63406e4f4c8d58161048b41b6f0bd8c; 5ac388db27c443dadfbb0b8b23fa7ccf429d901a up to, but not including, ca1c29f05274b737dc964e28b97803750d7cf7ec; 5ac388db27c443dadfbb0b8b23fa7ccf429d901a up to, but not including, dbaa37e060918c45517786e37ecab0f300b48fa9; 5ac388db27c443dadfbb0b8b23fa7ccf429d901a up to, but not including, a846aecb931b4d65d5eafa92a0623545af46d4f2; 6.6.120 up to, but not including, 6.6.148; 6.7fb46d134e1b8690bed2da9005b36d32d2efd34ac, b5029e91c63406e4f4c8d58161048b41b6f0bd8c, ca1c29f05274b737dc964e28b97803750d7cf7ec, dbaa37e060918c45517786e37ecab0f300b48fa9, a846aecb931b4d65d5eafa92a0623545af46d4f2, 6.6.148

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.