Bug 970378 - (CVE-2016-1956) VUL-0: CVE-2016-1956: MozillaFirefox: Linux video memory DOS with Intel drivers (MFSA 2016-19)
(CVE-2016-1956)
VUL-0: CVE-2016-1956: MozillaFirefox: Linux video memory DOS with Intel driv...
Status: RESOLVED DUPLICATE of bug 969894
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P3 - Medium : Normal
: ---
Assigned To: Security Team bot
Security Team bot
https://smash.suse.de/issue/162875/
CVSSv2:RedHat:CVE-2016-1956:5.1:(AV:N...
:
Depends on:
Blocks: 969894
  Show dependency treegraph
 
Reported: 2016-03-09 20:50 UTC by Victor Pereira
Modified: 2019-05-01 17:04 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Pereira 2016-03-09 20:50:12 UTC
rh#1315571

Security researcher Ucha Gobejishvili reported a denial of service (DOS) attack when doing certain WebGL operations in a canvas requiring an unusually large amount buffer to be allocated from video memory. This resulted memory resource exhaustion with some Intel video cards, requiring the computer to be rebooted to return functionality. This was resolved by putting in additional checks on the amount of memory to be allocated during graphics processing.

This issue was limited to a subset of Intel drivers on Linux. Other operating systems were not affected.



External Reference:

https://www.mozilla.org/security/announce/2016/mfsa2016-19.html

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1315571
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-1956
http://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-1956.html
Comment 1 Swamp Workflow Management 2016-03-09 23:00:34 UTC
bugbot adjusting priority
Comment 2 Marcus Meissner 2016-03-16 16:10:10 UTC
resolved in the main tracker bug 969894

*** This bug has been marked as a duplicate of bug 969894 ***