REDHAT-BUG-2039003: Medium severity libvirglrenderer vulnerability
The virgl forgets to initialize the memory pointed by the res->ptr when it creates resource. And the memory can be mapped to the guest kernel when the VIRTIOGPUCMDRESOURCEATTACHBACKING is issued. However, the guest userspace can read the data in the unintialized host memory by mmaping it from the guest kernel.
Upstream fix:
https://gitlab.freedesktop.org/virgl/virglrenderer/-/commit/b05bb61f454eeb8a85164c8a31510aeb9d79129c
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2039003?
The severity of REDHAT-BUG-2039003 is considered high due to potential information leakage from uninitialized memory.
How do I fix REDHAT-BUG-2039003?
To fix REDHAT-BUG-2039003, update to the latest version of the Freedesktop Virglrenderer where this issue has been addressed.
What are the potential impacts of REDHAT-BUG-2039003?
The potential impacts of REDHAT-BUG-2039003 include unauthorized access to sensitive data due to memory not being initialized properly.
Which software is affected by REDHAT-BUG-2039003?
The affected software for REDHAT-BUG-2039003 includes Freedesktop Virglrenderer.
When was REDHAT-BUG-2039003 reported?
REDHAT-BUG-2039003 was reported as a vulnerability recently impacting the Virglrenderer.