Issue 45705 in oss-fuzz: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_next_arhdr_wrlock

2022-03-20 Thread evv… via monorail via Elfutils-devel
Comment #3 on issue 45705 by evv...@gmail.com: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_next_arhdr_wrlock https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c3 Reproducer testcases are publicly available and can be downloaded using links in bug reports. Since every comment is

Issue 45630 in oss-fuzz: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str

2022-03-20 Thread evv… via monorail via Elfutils-devel
Comment #4 on issue 45630 by evv...@gmail.com: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c4 Issues like that are bogus and https://github.com/google/oss-fuzz/pull/7401 should fix them. Since it's a "security" is

Re: Some fuzzer workarounds

2022-03-20 Thread Evgeny Vereshchagin
Hi > Given that the new fuzz targets seem to just fail to compile with > ``` > projects/elfutils/fuzz-libdwfl.c:48:10: error: unused variable 'res' > [-Werror,-Wunused-variable] > Dwarf *res = dwfl_module_getdwarf(mod, &bias); > ^ > 1 error generated. > ``` I've just opened https://gith

Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names

2022-03-20 Thread evv… via monorail via Elfutils-devel
Comment #3 on issue 45636 by evv...@gmail.com: elfutils:fuzz-libdwfl: Crash in read_long_names https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45636#c3 It seems to be a duplicate of https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45628. Any idea why OSS-Fuzz keeps reporting it? I

[PATCH] configure: Don't check whether -m64 works for 32bit host biarch check

2022-03-20 Thread Mark Wielaard
Running a 32bit backtrace test against a 64bit binary doesn't work. Only a 64bit binary can backtrace a 32bit binary. So disable the biarch check that inserts -m64 for a 32bit host. https://sourceware.org/bugzilla/show_bug.cgi?id=24158 Signed-off-by: Mark Wielaard --- ChangeLog| 5 + co

[Bug general/28975] run-large-elf-file.sh fails in 32-bit cross-compile on 64-bit machine

2022-03-20 Thread mark at klomp dot org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=28975 Mark Wielaard changed: What|Removed |Added CC||mark at klomp dot org Assig

[PATCH] tests: Check addsections test binary is 64bit for run-large-elf-file.sh

2022-03-20 Thread Mark Wielaard
The test binary should be 64bit to be able to create 4GB, or larger, ELF files. https://sourceware.org/bugzilla/show_bug.cgi?id=28975 Signed-off-by: Mark Wielaard --- tests/ChangeLog | 4 tests/run-large-elf-file.sh | 11 +++ 2 files changed, 15 insertions(+) diff --g

[PATCH] libelf: Don't overflow offsets in elf_cvt_Verneed and elf_cvt_Verdef

2022-03-20 Thread Mark Wielaard
The conversion functions for Verdef and Verneed keep offsets to the next structure. Make sure that following vd_aux, vda_next, vd_next, vn_aux, vna_next and vn_next don't overflow (and wrap around) the offsets. Signed-off-by: Mark Wielaard --- libelf/ChangeLog | 7 ++ libelf/version_x

Issue 45705 in oss-fuzz: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_next_arhdr_wrlock

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45705 by da...@adalogics.com: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_next_arhdr_wrlock https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c2 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libdwfl-5085329

Issue 45705 in oss-fuzz: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_next_arhdr_wrlock

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #1 on issue 45705 by da...@adalogics.com: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_next_arhdr_wrlock https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45705#c1 ASAN report Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/leak-919ecedf38381f07ca17919209098f636c

Issue 45682 in oss-fuzz: elfutils:fuzz-libelf: Misaligned-address in elf_cvt_Verneed

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45682 by da...@adalogics.com: elfutils:fuzz-libelf: Misaligned-address in elf_cvt_Verneed https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45682#c2 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libelf-496858551930060

Issue 45682 in oss-fuzz: elfutils:fuzz-libelf: Misaligned-address in elf_cvt_Verneed

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #1 on issue 45682 by da...@adalogics.com: elfutils:fuzz-libelf: Misaligned-address in elf_cvt_Verneed https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45682#c1 UBSAN report Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-cf18cd9802d6953b96a96cb2364e46ade2dccdd

Issue 45646 in oss-fuzz: elfutils:fuzz-libdwfl: Misaligned-address in __libdw_image_header

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45646 by da...@adalogics.com: elfutils:fuzz-libdwfl: Misaligned-address in __libdw_image_header https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45646#c2 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libdwfl-56991716

Issue 45646 in oss-fuzz: elfutils:fuzz-libdwfl: Misaligned-address in __libdw_image_header

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #1 on issue 45646 by da...@adalogics.com: elfutils:fuzz-libdwfl: Misaligned-address in __libdw_image_header https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45646#c1 UBSAN report Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-137c106fe516c3a5c4d5fb8deeb45c4e9

Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45637 by da...@adalogics.com: elfutils:fuzz-libelf: Timeout in fuzz-libelf https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c2 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libelf-6393240885002240 684 bytes -

Issue 45637 in oss-fuzz: elfutils:fuzz-libelf: Timeout in fuzz-libelf

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #1 on issue 45637 by da...@adalogics.com: elfutils:fuzz-libelf: Timeout in fuzz-libelf https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45637#c1 ASAN report: Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-15f79e70f92567039dd67b7c3a16ad3a180b3a6e ALARM: work

Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45636 by da...@adalogics.com: elfutils:fuzz-libdwfl: Crash in read_long_names https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45636#c2 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libdwfl-5787862593830912 8.0 KB

Issue 45636 in oss-fuzz: elfutils:fuzz-libdwfl: Crash in read_long_names

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #1 on issue 45636 by da...@adalogics.com: elfutils:fuzz-libdwfl: Crash in read_long_names https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45636#c1 ASAN report = ==746==ERROR: AddressSanitizer: unknown-crash on address

Issue 45635 in oss-fuzz: elfutils:fuzz-libdwfl: Timeout in fuzz-libdwfl

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45635 by da...@adalogics.com: elfutils:fuzz-libdwfl: Timeout in fuzz-libdwfl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45635#c2 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libdwfl-5237809772888064 129 bytes

Issue 45635 in oss-fuzz: elfutils:fuzz-libdwfl: Timeout in fuzz-libdwfl

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #1 on issue 45635 by da...@adalogics.com: elfutils:fuzz-libdwfl: Timeout in fuzz-libdwfl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45635#c1 UBSAN report Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/timeout-2aaefec51e4f82909c4edd9ae287bf51b2eb6dd7 ALARM: wo

Issue 45634 in oss-fuzz: elfutils:fuzz-libdwfl: Misaligned-address in file_read_elf

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45634 by da...@adalogics.com: elfutils:fuzz-libdwfl: Misaligned-address in file_read_elf https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45634#c2 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libdwfl-506981816690278

Issue 45634 in oss-fuzz: elfutils:fuzz-libdwfl: Misaligned-address in file_read_elf

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #1 on issue 45634 by da...@adalogics.com: elfutils:fuzz-libdwfl: Misaligned-address in file_read_elf https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45634#c1 UBSAN report Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-59b5bfa44a73565527249e5a6d13b3c2

Issue 45631 in oss-fuzz: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libdw_gunzip

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45631 by da...@adalogics.com: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libdw_gunzip https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45631#c2 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libdwfl-574211

Issue 45631 in oss-fuzz: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libdw_gunzip

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #1 on issue 45631 by da...@adalogics.com: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libdw_gunzip https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45631#c1 MSAN report Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-cdd503eda6f927979a20a3bd

Issue 45630 in oss-fuzz: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #3 on issue 45630 by da...@adalogics.com: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c3 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libelf-5658767587

Issue 45630 in oss-fuzz: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45630 by da...@adalogics.com: elfutils:fuzz-libelf: Use-of-uninitialized-value in validate_str https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45630#c2 MSAN report: Running: /mnt/scratch0/clusterfuzz/bot/inputs/fuzzer-testcases/crash-ecd598ded30b07196a2ab343f59f7a2544

Issue 45629 in oss-fuzz: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_read_mmaped_file

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #3 on issue 45629 by da...@adalogics.com: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_read_mmaped_file https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45629#c3 (No comment was entered for this change.) Attachments: clusterfuzz-testcase-minimized-fuzz-libdwfl-52804764

Issue 45629 in oss-fuzz: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_read_mmaped_file

2022-03-20 Thread da… via monorail via Elfutils-devel
Comment #2 on issue 45629 by da...@adalogics.com: elfutils:fuzz-libdwfl: Indirect-leak in __libelf_read_mmaped_file https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45629#c2 ASAN report Indirect leak of 264 byte(s) in 1 object(s) allocated from: #0 0x524ae2 in __interceptor_calloc /sr