commit | 7c90d3d4b39fcf19253e161bd74601f6a8fb6e20 | [log] [tgz] |
---|---|---|
author | Daniel Cheng <dcheng@chromium.org> | Tue Nov 07 23:17:01 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 07 23:17:01 2023 |
tree | 62a44acd0b313d86585f502ce7d3f625dbc77dc8 | |
parent | 681e585407664232efebceaee369777d22e56b04 [diff] |
Initialize CoderErrorMgr when decoding JPEGs. Initialize CoderErrorMgr when decoding JPEGs. gfx::JPEGCodec::Decode() creates an uninitialized `CoderErrorMsg`, which contains a `jpeg_error_mgr`, which contains a `msg_parm` union. This union is used much later inside libjpeg_turbo: // From third_party/libjpeg_turbo/jerror.c:175: SNPRINTF(buffer, JMSG_LENGTH_MAX, msgtext, err->msg_parm.i[0], err->msg_parm.i[1], err->msg_parm.i[2], err->msg_parm.i[3], err->msg_parm.i[4], err->msg_parm.i[5], err->msg_parm.i[6], err->msg_parm.i[7]); libjpeg_turbo only initializes as many `msg_parm.i` entries as the corresponding format specifier consumes, relying on `SNPRINTF()` to ignore extra arguments. However, MSan still warns that this is a use of an uninitialized value, and indeed, the C standard says: If the format is exhausted while arguments remain, the excess arguments are evaluated (as always) but are otherwise ignored. Bug: 1369167 Change-Id: I35ac2bf7eecea6152d765de2015261f33cbe6615 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5008686 Reviewed-by: Leon Scroggins <scroggo@google.com> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1221255}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.