CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-46176 remediation guide

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support

In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix error path fall-through in mlx5_ib_dev_res_srq_init() mlx5_ib_dev_res_srq_init() allocates two SRQs, s0 and s1. When ib_create_srq() fails for s1, the error branch destroys s0 but falls through and unconditionally assigns the freed s0 and the ERR_PTR s1 to devr->s0 and devr->s1. This leads to several problems: the lock-free fast path checks "if (devr->s1) return 0;" and treats the ERR_PTR as already initialised; users in mlx5_ib_create_qp() dereference the freed SRQ or ERR_PTR via to_msrq(devr->s0)->msrq.srqn...

Open CVE record
ProductLinux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support
Affected versions>= b6334d2356fc0922ed01457960f74923058a353a < a13c2ac4d480b734342c6fbf8249fc48afd675f3, >= 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 < bc2cf5935b4665172235341163315905197ae91d, >= 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 < b087913ae88256df66620f7ba0a9776716aeef7e, >= 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 < 6fd93142dd1d09000c3750af08270f5792523fe9, >= 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 < c488df06bd552bb8b6e14fa0cfd5ad986c6e9525, >= 6.6.64 < 6.6.140, >= 6.11, >= 6.11 < 6.12.88, >= 6.13 < 6.18.30, >= 6.19 < 7.0.7, 7.1
Fixed versions6.6.140, 6.12.88, 6.18.30, 7.0.7
Priority basisReview · CVSS 7.8 · EPSS 0.14%
01

Identify the affected asset

Confirm whether Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support 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.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= b6334d2356fc0922ed01457960f74923058a353a < a13c2ac4d480b734342c6fbf8249fc48afd675f3, >= 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 < bc2cf5935b4665172235341163315905197ae91d, >= 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 < b087913ae88256df66620f7ba0a9776716aeef7e, >= 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 < 6fd93142dd1d09000c3750af08270f5792523fe9, >= 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467 < c488df06bd552bb8b6e14fa0cfd5ad986c6e9525, >= 6.6.64 < 6.6.140, >= 6.11, >= 6.11 < 6.12.88, >= 6.13 < 6.18.30, >= 6.19 < 7.0.7, 7.1. Treat incomplete inventory results as unresolved.

03

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.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.6.140, 6.12.88, 6.18.30, 7.0.7. Preserve configuration and rollback material before change.

05

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.