CVE-2026-53187
Last modified
CVE-2026-53187 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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.. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.17, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53187?
How severe is CVE-2026-53187?
How do I fix CVE-2026-53187?
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-53181In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53182In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53183In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53184In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53185In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53186In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-53188In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53189In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5319A security vulnerability has been detected in itsourcecode P…4.3
- CVE-2026-53190In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53191In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53192In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-53187?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
