drivers: counter: Fix possible out-of-bounds access in MCP7940N driver #84533
Conversation
This file contains 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
This PR fixes the issue of possible out-of-bounds access if write_data_block function was misused. Size argument of the function was only validated against the maximum allowed value, not the real size of the data struct to be read, what could cause accessing data past the boundary of the struct. Should fix zephyrproject-rtos#81930. Signed-off-by: Marcin Lyda <[email protected]>
Lefucjusz
force-pushed
the
fix_mcp7940_out_of_bounds_access
branch
from
437f700 to
7c576ac
Compare
Lefucjusz
changed the title
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.
This PR fixes the issue of possible out-of-bounds
access if write_data_block function was misused.
Size argument of the function was only validated
against the maximum allowed value, not the real
size of the data struct to be read, what could
cause accessing data past the boundary of the struct.
Should fix #81930.