Answer in brief
CVE-2026-46181 records a High severity (CVSS 7.8) vulnerability in RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-46181 records a High severity (CVSS 7.8) vulnerability in RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=30353bfc43a1602c020f31d95cf27182ffd23824 <1e2a44875b6afb4add1115f7f3351dcbeb6f273d || >=30353bfc43a1602c020f31d95cf27182ffd23824 <8b7833f3bce35cb0d01c1503781523c099c675f0 || >=30353bfc43a1602c020f31d95cf27182ffd23824 <c9341307ea16b9395c2e4c9c94d8499d91fe31d0 | 1e2a44875b6afb4add1115f7f3351dcbeb6f273d, 8b7833f3bce35cb0d01c1503781523c099c675f0, c9341307ea16b9395c2e4c9c94d8499d91fe31d0 |
| Linux/Linuxgeneric | 4.9 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=30353bfc43a1602c020f31d95cf27182ffd23824 <1e2a44875b6afb4add1115f7f3351dcbeb6f273d || >=30353bfc43a1602c020f31d95cf27182ffd23824 <8b7833f3bce35cb0d01c1503781523c099c675f0 || >=30353bfc43a1602c020f31d95cf27182ffd23824 <c9341307ea16b9395c2e4c9c94d8499d91fe31d0 | 1e2a44875b6afb4add1115f7f3351dcbeb6f273d, 8b7833f3bce35cb0d01c1503781523c099c675f0, c9341307ea16b9395c2e4c9c94d8499d91fe31d0 |
| Linux/Linuxgeneric | 4.9 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.