MDEV-40552 UBSAN: not a valid value for wkbByteOrder Gis_multi_point - #5471
Merged
Conversation
The byteorder field could contain an invalid value (> 1) on a GIS multi_point object where there byteorder was on any of the inner points. This can occur with any of the GIS "*FromWKB" functions that contained a multipoint object. This result in a invalid object being accepted and also potentially trigger undefined behaviour in the processing of the object.
raghunandanbhat
self-requested a review
July 30, 2026 07:47
raghunandanbhat
approved these changes
Jul 30, 2026
raghunandanbhat
left a comment
raghunandanbhat
left a comment
Contributor
There was a problem hiding this comment.
patch looks good. thanks @grooverdan
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.
The byteorder field could contain an invalid value (> 1) on a GIS multi_point object where there byteorder was on any of the inner points.
This can occur with any of the GIS "*FromWKB" functions that contained a multipoint object.
This result in a invalid object being accepted and also potentially trigger undefined behaviour in the processing of the object.