GH-49229: [C++] Fix abort when reading IPC file with a union validity bitmap and pre-buffering enabled#49230
Merged
Merged
Conversation
…lidity bitmap and pre-buffering enabled Found by OSS-Fuzz in https://issues.oss-fuzz.com/issues/482161154
Member
Author
|
@github-actions crossbow submit -g cpp |
pitrou
marked this pull request as ready for review
February 11, 2026 16:37
|
Revision: 1b01906 Submitted crossbow builds: ursacomputing/crossbow @ actions-3993aded3b
|
Member
Author
pitrou
added
the
Critical Fix
github-actions
Bot
added
awaiting merge
Mottl
pushed a commit
to Mottl/arrow
that referenced
this pull request
May 26, 2026
…lidity bitmap and pre-buffering enabled (apache#49230) ### Rationale for this change The logic for loading a Union array from a IPC file was inquiring whether a validity bitmap is present in a V4 metadata file (i.e. `buffers[0] != nullptr`). However, in the pre-buffering case, the buffers haven't been populated yet at the point, so the check would be ignored and the IPC file reader could happily create a Union array with a top validity bitmap. This could crash later in `UnionArray::SetData`. Found by OSS-Fuzz in https://issues.oss-fuzz.com/issues/482161154 ### Are these changes tested? By integration test and fuzz regression file. There are no unit tests in the C++ test suite that exercise V4 metadata IPC files with top-level union validity bitmaps. ### Are there any user-facing changes? No. **This PR contains a "Critical Fix".** This fixes a controlled crash when reading a pre-V5 IPC file with a top-level union validity bitmap and pre-buffering enabled. Instead a regular error will be returned. There are no known security implications. * GitHub Issue: apache#49229 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
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
2 participants
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.
Rationale for this change
The logic for loading a Union array from a IPC file was inquiring whether a validity bitmap is present in a V4 metadata file (i.e.
buffers[0] != nullptr). However, in the pre-buffering case, the buffers haven't been populated yet at the point, so the check would be ignored and the IPC file reader could happily create a Union array with a top validity bitmap. This could crash later inUnionArray::SetData.Found by OSS-Fuzz in https://issues.oss-fuzz.com/issues/482161154
Are these changes tested?
By integration test and fuzz regression file. There are no unit tests in the C++ test suite that exercise V4 metadata IPC files with top-level union validity bitmaps.
Are there any user-facing changes?
No.
This PR contains a "Critical Fix". This fixes a controlled crash when reading a pre-V5 IPC file with a top-level union validity bitmap and pre-buffering enabled. Instead a regular error will be returned. There are no known security implications.