CVE-2017-5956
UnknownEPSS 0.41%
Last modified
CVE-2017-5956 is a vulnerability of currently unknown severity. The vrend_draw_vbo function in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (out-of-bounds array access and QEMU process crash) via vectors involving vertext_buffer_index.. EPSS estimates a 0.41% chance of exploitation in the next 30 days.
Description
The vrend_draw_vbo function in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (out-of-bounds array access and QEMU process crash) via vectors involving vertext_buffer_index.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Virglrenderer Project | Virglrenderer | <= 0.5.0 |
References
- http://www.openwall.com/lists/oss-security/2017/02/13/2Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/96187Third Party Advisory, VDB Entry
- https://cgit.freedesktop.org/virglrenderer/commit/?id=a5ac49940c40ae415eac0cf912eac7070b4ba95dIssue Tracking, Patch, Third Party Advisory
- https://lists.freedesktop.org/archives/virglrenderer-devel/2017-February/000145.htmlPatch, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2017/02/13/2Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/96187Third Party Advisory, VDB Entry
- https://cgit.freedesktop.org/virglrenderer/commit/?id=a5ac49940c40ae415eac0cf912eac7070b4ba95dIssue Tracking, Patch, Third Party Advisory
- https://lists.freedesktop.org/archives/virglrenderer-devel/2017-February/000145.htmlPatch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5956?
The vrend_draw_vbo function in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (out-of-bounds array access and QEMU process crash) via vectors involving vertext_buffer_index.
How severe is CVE-2017-5956?
Severity scoring for CVE-2017-5956 is pending analysis. The EPSS model estimates a 0.41% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5956?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-5948An issue was discovered on OnePlus One, X, 2, 3, and 3T devi…
- CVE-2017-5949JavaScriptCore in WebKit, as distributed in Safari Technolog…
- CVE-2017-5950The SingleDocParser::HandleNode function in yaml-cpp (aka Li…
- CVE-2017-5951The mem_get_bits_rectangle function in base/gdevmem.c in Art…
- CVE-2017-5953vim before patch 8.0.0322 does not properly validate values …
- CVE-2017-5954An issue was discovered in the serialize-to-js package 0.5.0…
- CVE-2017-5957Stack-based buffer overflow in the vrend_decode_set_framebuf…5.5
- CVE-2017-5959CSRF token bypass in GeniXCMS before 1.0.2 could result in e…
- CVE-2017-5960An issue was discovered in Phalcon Eye through 0.4.1. The vu…
- CVE-2017-5961An issue was discovered in ionize through 1.0.8. The vulnera…
- CVE-2017-5962An issue was discovered in contexts_wurfl (for TYPO3) before…
- CVE-2017-5963An issue was discovered in caddy (for TYPO3) before 7.2.10. …
Are you affected by CVE-2017-5956?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
