Skip to content

Fix 32-bit overflow in LZW size calculation (MAX_CODE_LEN * lzwPos)#108

Open
uwezkhan wants to merge 2 commits intodloebl:mainfrom
uwezkhan:fix/lzw-size-multiplication-overflow
Open

Fix 32-bit overflow in LZW size calculation (MAX_CODE_LEN * lzwPos)#108
uwezkhan wants to merge 2 commits intodloebl:mainfrom
uwezkhan:fix/lzw-size-multiplication-overflow

Conversation

@uwezkhan
Copy link
Copy Markdown
Contributor

@uwezkhan uwezkhan commented Mar 1, 2026

This patch fixes a 32-bit arithmetic overflow in the LZW
byte list size calculations in cgif_raw.c.

The expression:

MAX_CODE_LEN * lzwPos

was evaluated using 32-bit arithmetic because
MAX_CODE_LEN is defined as an int and lzwPos is uint32_t.
Under C's usual arithmetic conversions, the multiplication
is performed as uint32_t before being widened to 64-bit
for the subsequent division.

If lzwPos is sufficiently large, the intermediate
32-bit multiplication can wrap around, resulting in an
incorrect (truncated) buffer size being passed to malloc().

The fix casts MAX_CODE_LEN to uint64_t:

(uint64_t)MAX_CODE_LEN * lzwPos

This ensures the multiplication is performed in 64-bit
arithmetic and prevents intermediate overflow.

No API changes.
No behavioral changes for valid inputs.
Negligible runtime impact.

@dloebl
Copy link
Copy Markdown
Owner

dloebl commented Mar 15, 2026

Hey @uwezkhan,
please read the contributing guidelines before opening any new pull requests or issues.

Missing test case (required): Bug fix PRs must include a test in tests/ that reproduces the issue on main (fails before the fix, passes after). No test was provided and no changes to tests/meson.build were made. See CONTRIBUTING.md:, section "Submitting Pull Requests", item 3.

AI tooling attribution: If any AI models or tooling were used to produce this PR, please disclose that per our contributing guidelines (CONTRIBUTING.md:, item 5).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants