CVE-2017-5993: Medium severity Virglrenderer Project Virglrenderer vulnerability
Memory leak in the vrendrendererinitblitctx function in vrendblitter.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRGLCCMDBLIT commands.
Other sources
Virgil 3d project, used by Quick Emulator(Qemu) to implement 3D GPU support for the virtio GPU, is vulnerable to memory leakage issue. It could occur when a guest tries to initialise blitter context via 'VIRGLCCMDBLIT' command.
A guest user/process could use this flaw to leak host memory resulting in DoS.
Upstream patch: --------------- -> https://cgit.freedesktop.org/virglrenderer/commit/?id=6eb13f7a2dcf391ec9e19b4c2a79e68305f63c22
Reference: ---------- -> http://www.openwall.com/lists/oss-security/2017/02/15/7
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
virglrendererto a version that resolves this vulnerability.Fixed in 0.6.0 - Compensating control
For virtio GPU 3D blit handling, prevent or restrict untrusted guest access to the VIRGL_CCMD_BLIT command so a guest cannot repeatedly trigger vrend_renderer_init_blit_ctx memory leakage.
Event History
Frequently Asked Questions
What is the severity of CVE-2017-5993?
CVE-2017-5993 has a medium severity level as it can lead to denial of service through memory consumption.
How do I fix CVE-2017-5993?
To fix CVE-2017-5993, upgrade virglrenderer to version 0.6.0 or later.
Who is affected by CVE-2017-5993?
Local guest OS users on systems using virglrenderer versions before 0.6.0 are affected by CVE-2017-5993.
What systems are impacted by CVE-2017-5993?
CVE-2017-5993 impacts systems utilizing virglrenderer versions up to 0.5.0.
What could an attacker do with CVE-2017-5993?
An attacker could exploit CVE-2017-5993 to execute a denial of service attack by sending a large number of VIRGL_CCMD_BLIT commands.