Re: Issue 440177309: elfutils:fuzz-libdwfl: Use-of-uninitialized-value in __libelf_read_mmaped_file

Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/440177309 Changed ev...@gmail.com added comment #2: Valgrind reports an invalid read here. It can be reproduced by downloading the testcase from https://o

Re: [PATCH v2] __libdw_dieabbrev: Replace rwlock with __atomic builtins

Hi Mark, On Fri, Sep 5, 2025 at 10:49 AM Mark Wielaard wrote: > > Hi Aaron, > > On Thu, 2025-09-04 at 14:10 -0400, Aaron Merey wrote: > > On Thu, Sep 4, 2025 at 10:40 AM Mark Wielaard wrote: > > > On Mon, 2025-09-01 at 20:31 -0400, Aaron Merey wrote: > > > > __libdw_dieabbrev uses the abbrev_loc

Re: Issue 443254909: elfutils:fuzz-libdwfl: Crash in __elf64_getphdr_wrlock

Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/443254909 Changed ev...@gmail.com added comment #2: I haven't been able to reproduce it locally with the toolchain provided by OSS-Fuzz but Valgrind reports

Re: [PATCH] libdw_open_elf: Avoid invalid free

Hi Aaron, On Fri, Sep 05, 2025 at 03:41:53PM -0400, Aaron Merey wrote: > If libdw_open_elf detects an invalid ELF file, it may attempt to > temporarily treat it as an ELF archive in order to check if there's > a valid ELF file following a header. > > When doing this, the elf descriptor for the in

Issue 443254909: elfutils:fuzz-libdwfl: Crash in __elf64_getphdr_wrlock

Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/443254909 Reference Info: 443254909 elfutils:fuzz-libdwfl: Crash in __elf64_getphdr_wrlock component: Public Trackers > 1362134 > OSS Fuzz status: New repo

☺ Buildbot (Sourceware): elfutils - build successful (main)

A restored build has been detected on builder elfutils-debian-i386 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/17/builds/539 Build state: build successful Revision: 73a287ee405fbb44c8c05be1d065cb48ebe13f33 Worker: debian-i386-2 B

☺ Buildbot (Sourceware): elfutils - build successful (main)

A restored build has been detected on builder elfutils-debian-ppc64 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/63/builds/550 Build state: build successful Revision: 3676da22da806a3c8c5948311b0c8ce17c8d5fd8 Worker: debian-ppc64 B

☠ Buildbot (Sourceware): elfutils - failed test (failure) (main)

A new failure has been detected on builder elfutils-debian-ppc64 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/63/builds/549 Build state: failed test (failure) Revision: 7a8a59b24280f4dcf533c95e5f74edbc315bfb36 Worker: debian-ppc64

Re: Issue 442161254: elfutils:fuzz-libdwfl: Crash in load_shdr_wrlock

Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/442161254 Changed ev...@gmail.com added comment #2: I haven't been able to reproduce it locally yet with the testcase I downloaded from https://oss-fuzz.com

Re: Issue 440144412: elfutils:fuzz-libdwfl: Check failed in CheckUnwind

Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/440144412 Changed ev...@gmail.com added comment #2: It can be reproduced by building elfutils with ASan, downloading the testcase from https://oss-fuzz.com/

☠ Buildbot (Sourceware): elfutils - failed test (failure) (main)

A new failure has been detected on builder elfutils-debian-i386 while building elfutils. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/17/builds/538 Build state: failed test (failure) Revision: 20b0dae7eb2ce48ee9fb5d4f41352b2c99efd066 Worker: debian-i386 B

Re: Issue 440209728: elfutils:fuzz-libdwfl: Abrt in elf_end

Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/440209728 Changed ev...@gmail.com added comment #2: It can be reproduced by building elfutils with ASan, downloading the testcase from https://oss-fuzz.com/

Re: Issue 441055980: elfutils:fuzz-libdwfl: Heap-buffer-overflow in gelf_getshdr

Replying to this email means your email address will be shared with the team that works on this product. https://issues.oss-fuzz.com/issues/441055980 Changed ev...@gmail.com added comment #2: It can be reproduced by building elfutils with ASan, downloading the testcase from https://oss-fuzz.com/

Re: [PATCH v2] __libdw_dieabbrev: Replace rwlock with __atomic builtins

Hi Frank, On Thu, 2025-09-04 at 14:30 -0400, Frank Ch. Eigler wrote: > > > > Maybe we just have to say that you cannot share Dwarf_Die references > > > > between threads? So if you want to use a Dwarf_Die from another thread > > > > you have to copy it instead by passing it by reference? [...] > >

Re: [PATCH v2] __libdw_dieabbrev: Replace rwlock with __atomic builtins

Hi Aaron, On Thu, 2025-09-04 at 14:10 -0400, Aaron Merey wrote: > On Thu, Sep 4, 2025 at 10:40 AM Mark Wielaard wrote: > > On Mon, 2025-09-01 at 20:31 -0400, Aaron Merey wrote: > > > __libdw_dieabbrev uses the abbrev_lock rwlock to synchronize access to the > > > Dwarf_Die abbrev field as well as

Re: [PATCH] elf_getdata_rawchunk.c: Fix dummy chunk insertion race condition

Hi Aaron, I did a quick check for this unlock read lock, aqcuire write lock pattern in the code which we should double check/document/fix if necessary: https://sourceware.org/bugzilla/show_bug.cgi?id=33382 On Thu, 2025-09-04 at 14:24 -0400, Aaron Merey wrote: > When elf_getdata_rawchunk aquires a