Validate decoded ISO gain-map numeric metadata - #456
Open
gregbenz wants to merge 1 commit into
Open
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
gregbenz
marked this pull request as ready for review
August 18, 2026 19:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Validate decoded ISO gain-map numeric metadata
Summary
Why
Malformed ISO gain-map metadata could make
uhdr_dec_probe()succeed even when metadata conversion failed. That could expose invalid or uninitialized values to callers and allow non-finite values to reach gain-map calculations. The HEIF/AVIF decode error path also returned before releasing objects it had already created.This change validates exact rational bounds and converted values before use, then returns the existing metadata error to the caller. It intentionally preserves valid signed offsets and does not add trailing-byte restrictions, keeping versioned payload compatibility policy separate.
Testing
Addresses the numeric-validation portion of #446; version-aware trailing-byte and payload-size
policy is intentionally left for separate follow-up.