CVE-2026-53187·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.13
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.12% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-53187 scores 7.1 on CVSS, so a successful attack would be serious — but at 0.12%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.13
Fixed in: 7.0.13
How to fix this CVE
Update your Linux kernel to version 7.0.13 or later to patch CVE-2026-53187. This vulnerability allows unprivileged local users to trigger out-of-bounds memory reads through malformed CPU ID parameters in RDMA device memory allocation requests. Affected systems running kernel versions 6.19 through 7.0.12 should prioritize this kernel update to prevent potential denial of service or information disclosure.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Run `uname -r` to check the current kernel version; versions 6.19 through 7.0.12 are vulnerable
- Check if RDMA/InfiniBand drivers are loaded with `lsmod | grep rdma` or `lsmod | grep ib_`
- Review systemd journal for cpumask validation errors with `journalctl -xe | grep cpumask`
- After patching, verify the new kernel is active with `uname -r` and confirm it matches version 7.0.13 or later
FAQ
What is CVE-2026-53187?
CVE-2026-53187 is a kernel vulnerability in RDMA memory allocation that fails to validate user-supplied CPU ID values before performing bitmap operations, potentially causing out-of-bounds memory reads or system panics on systems with CONFIG_DEBUG_PER_CPU_MAPS enabled.
Is CVE-2026-53187 being actively exploited?
No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits are currently available. However, it can be triggered by any unprivileged local user with RDMA capabilities.
What versions of Kernel are affected by CVE-2026-53187?
Linux kernel versions 6.19 through 7.0.12 are vulnerable. Kernel 7.0.13 and later versions contain the fix.
How do I check if my server is vulnerable to CVE-2026-53187?
Run `uname -r` to display your kernel version; if it shows 6.19.x through 7.0.12, your system is vulnerable. Additionally, check if RDMA is in use with `grep -i rdma /proc/modules`.
Does Defensia detect CVE-2026-53187?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-53187 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-53187. Free for 1 server.
Get started free