Answer in brief
CVE-2026-53187 records a High severity (CVSS 7.1) vulnerability in RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc. 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.1. 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 | >=d83edab562a496a42720902a1d2effccd05c37c5 <bd5e818be7964c1689fba2dad9e6bd3a827fee74 || >=d83edab562a496a42720902a1d2effccd05c37c5 <0efbb6b54ff56300867027d8e0800d0e32226a20 || >=d83edab562a496a42720902a1d2effccd05c37c5 <323c98a4ff06aa28114f2bf658fb43eb3b536bbc | bd5e818be7964c1689fba2dad9e6bd3a827fee74, 0efbb6b54ff56300867027d8e0800d0e32226a20, 323c98a4ff06aa28114f2bf658fb43eb3b536bbc |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc The cpu_id attribute supplied by user space through UVERBS_ATTR_ALLOC_DMAH_CPU_ID is passed directly to cpumask_test_cpu() without first verifying that the value is within the valid CPU range. Passing such untrusted data to cpumask_test_cpu() may lead to an out-of-bounds read of the underlying cpumask bitmap: the helper expands to a test_bit() that indexes the bitmap by cpu_id / BITS_PER_LONG with no bound check. In addition, on kernels built with CONFIG_DEBUG_PER_CPU_MAPS it trips the WARN_ON_ONCE() in cpumask_check(); combined with panic_on_warn this turns a bad user input into a machine reboot. Reject any cpu_id that is not smaller than nr_cpu_ids with -EINVAL before it is used. Reported by Smatch.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-53187 records a High severity (CVSS 7.1) vulnerability in RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc. 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.1. 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 | >=d83edab562a496a42720902a1d2effccd05c37c5 <bd5e818be7964c1689fba2dad9e6bd3a827fee74 || >=d83edab562a496a42720902a1d2effccd05c37c5 <0efbb6b54ff56300867027d8e0800d0e32226a20 || >=d83edab562a496a42720902a1d2effccd05c37c5 <323c98a4ff06aa28114f2bf658fb43eb3b536bbc | bd5e818be7964c1689fba2dad9e6bd3a827fee74, 0efbb6b54ff56300867027d8e0800d0e32226a20, 323c98a4ff06aa28114f2bf658fb43eb3b536bbc |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc The cpu_id attribute supplied by user space through UVERBS_ATTR_ALLOC_DMAH_CPU_ID is passed directly to cpumask_test_cpu() without first verifying that the value is within the valid CPU range. Passing such untrusted data to cpumask_test_cpu() may lead to an out-of-bounds read of the underlying cpumask bitmap: the helper expands to a test_bit() that indexes the bitmap by cpu_id / BITS_PER_LONG with no bound check. In addition, on kernels built with CONFIG_DEBUG_PER_CPU_MAPS it trips the WARN_ON_ONCE() in cpumask_check(); combined with panic_on_warn this turns a bad user input into a machine reboot. Reject any cpu_id that is not smaller than nr_cpu_ids with -EINVAL before it is used. Reported by Smatch.
Quoted source text, attributed separately from HOL analysis.