[Bug libelf/23528] When executing ./eu-nm or ./eu-readelf -aAdehIlnrsSVcp -w, AddressSanitizer catch a double-free crash. (CVE-2018-16402)

2020-04-08 Thread fweimer at redhat dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=23528

Florian Weimer  changed:

   What|Removed |Added

 CC||fweimer at redhat dot com
Summary|When executing ./eu-nm or   |When executing ./eu-nm or
   |./eu-readelf|./eu-readelf
   |-aAdehIlnrsSVcp -w, |-aAdehIlnrsSVcp -w,
   |AddressSanitizer catch a|AddressSanitizer catch a
   |double-free crash.  |double-free crash.
   ||(CVE-2018-16402)
  Alias||CVE-2018-16402

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug debuginfod/27758] security idea: DEBUGINFOD_VERIFY mode

2021-04-21 Thread fweimer at redhat dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=27758

Florian Weimer  changed:

   What|Removed |Added

 CC||fweimer at redhat dot com

--- Comment #4 from Florian Weimer  ---
And it should be possible to use the Content-Length header to verify that the
data does not have an excessive size (something that is not possible with just
the hash itself).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug general/28263] 0.185: test suite fails with sigsegv

2021-08-25 Thread fweimer at redhat dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=28263

Florian Weimer  changed:

   What|Removed |Added

 CC||fweimer at redhat dot com
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Florian Weimer  ---
I believe this was already fixed as:

commit 9aee0992d6e6ec4cce2c015d8da4b61022c6f6dd
Author: Mark Wielaard 
Date:   Wed Aug 4 21:01:27 2021 +0200

tests: Allow an extra pthread_kill frame in backtrace tests

glibc 2.34 calls pthread_kill from the raise function. Before raise
directly called the (tg)kill syscall. So allow pthread_kill to be the
first frame in a backtrace where raise is expected. Also change some
asserts to fprintf plus abort to make it more clear why the testcase
fails.

https://sourceware.org/bugzilla/show_bug.cgi?id=28190

Signed-off-by: Mark Wielaard 

*** This bug has been marked as a duplicate of bug 28190 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libelf/28190] FAIL: run-backtrace-native.sh with glibc 2.34

2021-08-25 Thread fweimer at redhat dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=28190

Florian Weimer  changed:

   What|Removed |Added

 CC||kloczko.tomasz at gmail dot com

--- Comment #8 from Florian Weimer  ---
*** Bug 28263 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/28495] New: Add support for SHT_RELR to eu-readelf

2021-10-25 Thread fweimer at redhat dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=28495

Bug ID: 28495
   Summary: Add support for SHT_RELR to eu-readelf
   Product: elfutils
   Version: unspecified
Status: NEW
  Severity: enhancement
  Priority: P2
 Component: tools
  Assignee: unassigned at sourceware dot org
  Reporter: fweimer at redhat dot com
CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

glibc is considering adding SHT_RELR/DT_RELR support:

ld.so: Support DT_RELR relative relocation format
https://sourceware.org/bugzilla/show_bug.cgi?id=27924

eu-readelf -r needs to print these relocations, too.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug tools/28495] Add support for SHT_RELR to eu-readelf

2021-10-26 Thread fweimer at redhat dot com via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=28495

Florian Weimer  changed:

   What|Removed |Added

 CC||fweimer at redhat dot com

--- Comment #2 from Florian Weimer  ---
There is no official wording yet. The generic-abi thread is all we have at the
moment: https://groups.google.com/g/generic-abi/c/bX460iggiKg

Sorry. Maybe I was a bit too proactive in filing this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.