NAS-141769 / 25.10.5 / NTB: ntb_transport: validate length in frame header (by amotin)#315
Merged
Merged
Conversation
In case consumer provide receive buffer bigger than frame size, misbehaving peer can cause read beyond the frame end. Explicit check should prevent it. (cherry picked from commit fb01b8b)
Author
yocalebo
approved these changes
Jul 13, 2026
Author
|
This PR has been merged and conversations have been locked. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
In case consumer provide receive buffer bigger than frame size, misbehaving peer can cause read beyond the frame end. Explicit check should prevent it.
Original PR: #314