First published: Mon Jan 10 2022(Updated: )
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 VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING is issued. However, the guest userspace can read the data in the unintialized host memory by mmaping it from the guest kernel. Upstream fix: <a href="https://gitlab.freedesktop.org/virgl/virglrenderer/-/commit/b05bb61f454eeb8a85164c8a31510aeb9d79129c">https://gitlab.freedesktop.org/virgl/virglrenderer/-/commit/b05bb61f454eeb8a85164c8a31510aeb9d79129c</a>
Affected Software | Affected Version | How to fix |
---|---|---|
libvirglrenderer |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2039003 is considered high due to potential information leakage from uninitialized memory.
To fix REDHAT-BUG-2039003, update to the latest version of the Freedesktop Virglrenderer where this issue has been addressed.
The potential impacts of REDHAT-BUG-2039003 include unauthorized access to sensitive data due to memory not being initialized properly.
The affected software for REDHAT-BUG-2039003 includes Freedesktop Virglrenderer.
REDHAT-BUG-2039003 was reported as a vulnerability recently impacting the Virglrenderer.