CVE-2026-46181 remediation guide
Linux Linux, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() Sashiko points out the radix_tree itself is RCU safe, but nothing ever frees the mlx4_srq struct with RCU, and it isn't even accessed within the RCU critical section. It also will crash if an event is delivered before the srq object is finished initializing. Use the spinlock since it isn't easy to make RCU work, use refcount_inc_not_zero() to protect against partially initialized objects, and order the refcount_set() to be after the srq is fully initialized.
Identify the affected asset
Confirm whether Linux Linux, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8 is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 30353bfc43a1602c020f31d95cf27182ffd23824 < 1e2a44875b6afb4add1115f7f3351dcbeb6f273d, >= 30353bfc43a1602c020f31d95cf27182ffd23824 < 8b7833f3bce35cb0d01c1503781523c099c675f0, >= 30353bfc43a1602c020f31d95cf27182ffd23824 < c9341307ea16b9395c2e4c9c94d8499d91fe31d0, >= 4.9, >= 4.9 < 6.18.30, >= 6.19 < 7.0.7, 7.1. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 6.18.30, 7.0.7. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.