CVE-2026-53187

RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc

Published Jun 25, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw resides in the Linux kernel’s RDMA subsystem. User space can pass a CPU identifier through UVERBS_ATTR_ALLOC_DMAH_CPU_ID without kernel validation. The value is directly supplied to cpumask_test_cpu(), which can read beyond the end of the CPU mask bitmap. This vulnerability corresponds to CWE‑125 (Out‑of‑Bounds Read) and CWE‑787 (Out‑of‑Bounds Write). When a kernel built with CONFIG_DEBUG_PER_CPU_MAPS is used, the missing check triggers WARN_ON_ONCE; if panic_on_warn is enabled, the untrusted input can reliably cause a system reboot. The only direct impact is a denial of service via an out‑of‑bounds read, with no known path for information disclosure or privilege escalation, as the code path is confined within the kernel’s RDMA handling.

Affected Systems

All Linux kernel releases containing the RDMA core and uverbs driver before the applied fix are affected. The vulnerability is not limited to a specific version string, so any kernel compiled with RDMA support that omitted the patch is vulnerable. Systems that load the RDMA core module or have it built into the kernel at boot are at risk.

Risk and Exploitability

The CVSS score is 7.1, and EPSS is <1%, indicating low exploitation likelihood, while the flaw is not listed in CISA’s KEV catalog. Attack requires a local user or process with the UVERBS interface. Because the exploit path involves unvalidated user data, the difficulty of exploitation is moderate to high: the attacker must supply a kernel‑space allocation request with an out‑of‑range CPU ID. No public exploits exist, but the return to a system reboot renders the flaw severe for impacted environments, especially those compiled with panic_on_warn turned on.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that incorporates the fix for the RDMA core CPU‑ID validation
  • If upgrading is not immediately possible, disable RDMA support or unload the rdma-core module on affected systems
  • Configure the kernel to disable panic_on_warn or disable CONFIG_DEBUG_PER_CPU_MAPS when RDMA drivers are used, to prevent a reboot from the corrupted read

Generated by OpenCVE AI on August 12, 2026 at 07:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8726-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8727-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-2 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-3 Linux kernel (IBM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8800-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-2 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-4 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H'}

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-125
Type Values Removed Values Added
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.
Title RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 7:57 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Modified
Published
Jun 25, 2026, 9:16 AM
Modified
Oct 19, 2026, 8:19 PM
Severity
Moderate
Public date
Jun 25, 2026, 12:00 AM