CVE-2026-46176
Last modified
CVE-2026-46176 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6.64, < 6.6.140 | — |
| Linux | Linux Kernel | >= 6.11, < 6.12.88 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.30 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.7 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-46176?
How severe is CVE-2026-46176?
How do I fix CVE-2026-46176?
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-46170In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46171In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46172In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46173In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46174In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-46175In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-46177In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-46178In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46179In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46180In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46181In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46182In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-46176?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
