fsck.vfat invalid memory access in get_fat #12
Closed
Comments
Thank you very much, that was a nasty one: FAT12 corruption when a certain FAT entry at the end is changed. That bug has existed since very old versions, maybe right from the start. Fixed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This file will generate some invalid memory read in fsck.vfat:
https://crashes.fuzzing-project.org/dosfstools-get_fat-invalid-read
Judging from the output of address sanitizer and valgrind it is a bit unusual, it seems to be neither memory on the stack or heap, but it also doesn't crash the app if run without asan or valgrind. Happens both with the latest release and latest git code.
Found with american fuzzy lop.
This is the address sanitizer stack trace:
The text was updated successfully, but these errors were encountered: