REDHAT-BUG-1310570: High severity Linux Kernel Linux vulnerability
It was reported that drivers/infiniband stack uses write() as a replacement for bi-directional ioctl(), which is not safe. There are ways to trigger write calls that result in the return structure that is normally written to user space being shunted off to user specified kernel memory instead.
A local unprivileged user on a system with rdmaucm module loaded could use this flaw to escalate their privileges.
Upstream patch:
https://git.kernel.org/linus/e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3
CVE-ID request and assignment:
http://seclists.org/oss-sec/2016/q2/269 http://seclists.org/oss-sec/2016/q2/274
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux Kernelto a version that resolves this vulnerability.Patch e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3 - Remove
Remove
rdma_ucm modulefrom your environment.Unload and blacklist the rdma_ucm kernel module until a kernel containing the upstream patch (commit e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3) is deployed to prevent local unprivileged users from exploiting this issue.
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-1310570?
The severity of REDHAT-BUG-1310570 is considered high due to potential arbitrary memory access risks.
How do I fix REDHAT-BUG-1310570?
To fix REDHAT-BUG-1310570, update to the latest patched version of the affected Linux kernel.
What systems are affected by REDHAT-BUG-1310570?
REDHAT-BUG-1310570 affects systems running the vulnerable versions of the Linux kernel utilizing the infiniband stack.
What are the potential impacts of exploiting REDHAT-BUG-1310570?
Exploiting REDHAT-BUG-1310570 can lead to unauthorized access to kernel memory and potential system compromise.
How can I determine if my system is vulnerable to REDHAT-BUG-1310570?
You can determine if your system is vulnerable to REDHAT-BUG-1310570 by checking your kernel version against the known vulnerable versions.