Closed thesamesam closed 4 months ago
This looks like it has been fixed upstream. I just tried building with --enable-hardening with FORTIFY_SOURCE set to 3, and running the regression test, and it's passing 100%. I suspect it was fixed when we added --enable-asan and --enable-ubsan and fixed up any issues that were detected by these sanitizers.
Noticed when running unblob's test suite.
A smaller reproducer is:
This is with GCC 13.1.1 20230701,
-D_FORTIFY_SOURCE=3
, glibc-2.37, and e2fsprogs-1.47.0 on amd64.Attached f_badsymlinks.img (from the unblob test suite): f_badsymlinks.img.gz