Multiple vulnerabilities have been reported in Google Chrome, where some have an unknown impact while others can be exploited by malicious people bypass certain security restrictions, disclose system information, and compromise a user's system.

1) An error when handling sandboxed frames can be exploited to navigate to or close the top location.

2) An unspecified error can lead to cross-origin message leaks.

3) An error related to counter nodes can be exploited to corrupt memory.

4) An error when handling box layout may lead to a stale node.

5) An error in certain workers can lead to cross-origin message leaks.

6) A use-after-free error exists within the DOM URL handling.

7) An error when handling unicode ranges can be exploited to cause an out-of-bounds read.

This vulnerability affects builds for Linux only.

8) An error in v8 can be exploited to bypass the same origin policy.

9) An unspecified error allows bypassing the pop-up blocker.

10) A use-after-free error exists within the document script lifetime handling.

11) An error within the OGG container can be exploited to cause an out-of-bounds write.

12) An error when handling table painting may lead to a stale pointer.

13) An error within the video code may result in use of corrupt out-of-bounds structures.

14) An unspecified error exists in the handling of the DataView object.

15) An error related to a bad cast exists within the handling of text rendering.

16) An error in the WebKit context code can lead to a stale pointer.

17) An error in XSLT may leak heap addresses.

18) An error in the handling of SVG cursors can lead to a stale pointer.

19) An error when handling attributes can be exploited to corrupt the DOM tree.

20) An error when handling re-entrancy of RegExp code can lead to memory corruption.

21) An error in v8 can be exploited to access invalid memory.

The vulnerabilities are reported in versions prior to 10.0.648.127.

Solution
Upgrade to version 10.0.648.127.

Provided and/or discovered by
The vendor credits:
1) sirdarckcat, Google Security Team.
2, 5, 8) Daniel Divricean.
3, 4, 12) Martin Barbella.
6, 14, 16, 18, 19) Sergey Glazunov.
7, 10, 15) miaubiz.
9) Chamal de Silva.
11) SkyLined, Google Chrome Security Team (SkyLined) and David Weston, MSVR.
13) Tavis Ormandy, Google Security Team.
17) Chris Evans, Google Chrome Security Team.
20, 21) Christian Holler.

Changelog
Further details available to Secunia VIM customers

Original Advisory
http://googlechromereleases.blogspot.com/2011/03/chrome-stable-release.html

Deep Links
Links available to Secunia VIM customers