Google V8, as used in Google Chrome before 34.0.1847.116, does not properly implement lazy deoptimization, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code, as demonstrated by improper handling of a heap allocation of a number outside the Small Integer (aka smi) range.
https://code.google.com/p/v8/source/detail?r=19834
https://code.google.com/p/chromium/issues/detail?id=350434
http://www.debian.org/security/2014/dsa-2905
http://security.gentoo.org/glsa/glsa-201408-16.xml
http://lists.opensuse.org/opensuse-updates/2014-05/msg00012.html
http://googlechromereleases.blogspot.com/2014/04/stable-channel-update.html