In flt_readdir(), do not write into the buffer returned by readdir() #1
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
When adjusting file names, flt_readdir() assumes that the de->d_name points to a buffer that has sufficient size to accomodate the new name. However, readdir() does not makes any guarantee about that at all. In practice, I've seen de->d_name pointing to tightly packed memory, such that overwriting past the original name ends up corrupting data in the directory stream, leading to erratic undefined behavior. (In my case, the directory offset became corrupted, leading to an infinite directory scanning loop.) This commit fixes the issue by copying the name into some local buffer before making changes to it. Also, I took the liberty to sprinkle some more debug statements while I'm at it.
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.
When adjusting file names,
flt_readdir()assumes thatde->d_namepoints to a buffer that has sufficient size to accommodate the new name. However,readdir()does not makes any guarantee about that at all.In practice, I've seen
de->d_namepointing to tightly packed memory, such that overwriting past the original name ends up corrupting data in the directory stream, leading to erratic undefined behaviour. (In my case, the directory offset became corrupted, leading to an infinite directory scanning loop.)This commit fixes the issue by copying the name into some local buffer before making changes to it. Also, I took the liberty to sprinkle some more debug statements while I'm at it.