librtas: fix buffer length determination in rtas_set_sysparm() #35
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 data passed by callers has this layout:
struct {
uint8_t len_msb;
uint8_t len_lsb;
char payload[];
};
I.e. the length of valid data in payload[] is stored in the first two bytes of the buffer. However, rtas_set_sysparm() wrongly assumes that the length is in host-endian, leading to miscalculation of allocation and copy sizes.
For example, given this code in rtas_set_sysparm():
int rtas_set_sysparm(unsigned int parameter, char *data) {
...
size = *(short *)data;
...
memcpy(kernbuf, data, size + sizeof(short));
...
}
on little-endian targets, the following code:
results in a copy of size ((6 << 8) + 2) = 1538, reading beyond the end of the passed object.
Similarly, objects with an encoded size of 256 or greater will result in copying too little data.
Extract the size from the buffer correctly, always treating it as big-endian.