CVE-2026-53188·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Validate the passed in fops for ib_get_ucaps() Sashiko pointed out it is not safe to rely only on the devt because char/block alias so if the user finds a block device with the same dev_t it can masquerade as a ucap cdev fd. Test the f_ops to only accept authentic cdevs.
- 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.11% — higher than 1% 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-53188 scores 8.8 on CVSS, so a successful attack would be serious — but at 0.11%, 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 a vulnerability in the RDMA/core subsystem that could allow privilege escalation. The vulnerability exists in the ib_get_ucaps() function, which failed to properly validate character device file operations, potentially allowing attackers with local access to masquerade as legitimate RDMA capability devices. Ensure your system is running a patched kernel version to mitigate this local privilege escalation risk.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your installed kernel version with 'uname -r' and compare against the affected range 6.19 to 7.0.12
- Step 2: Verify if RDMA/InfiniBand subsystem is enabled by checking 'lsmod | grep rdma' or 'grep CONFIG_INFINIBAND /boot/config-$(uname -r)'
- Step 3: Search kernel logs for RDMA-related errors using 'sudo dmesg | grep -i rdma' or 'sudo journalctl -u kernel | grep -i rdma' to identify potential exploitation attempts
- Step 4: Confirm the kernel patch is applied by checking if your version is 7.0.13 or later with 'uname -r' and verifying commit 4a1b1ac2744694a2ecd66a84bdb1445f4ef24bee exists in your kernel source
FAQ
What is CVE-2026-53188?
This vulnerability allows a local attacker with user-level privileges to escalate their access by exploiting insufficient validation in the RDMA capability device interface. An attacker could use a block device with the same device number to impersonate a legitimate RDMA character device, bypassing security controls that rely solely on device identification.
Is CVE-2026-53188 being actively exploited?
No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits have been disclosed. However, the local nature and privilege escalation potential make it a significant threat in multi-tenant environments.
What versions of Kernel are affected by CVE-2026-53188?
Linux kernel versions 6.19 through 7.0.12 are vulnerable. The fix is included in kernel version 7.0.13 and later.
How do I check if my server is vulnerable to CVE-2026-53188?
Run 'uname -r' to check your kernel version. If it shows a version between 6.19 and 7.0.12, your system is vulnerable. Verify RDMA support is enabled with 'lsmod | grep rdma' to determine actual exposure.
Does Defensia detect CVE-2026-53188?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-53188 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-53188. Free for 1 server.
Get started free