Issue 46192 in oss-fuzz: elfutils:fuzz-libdwfl: Out-of-memory in fuzz-libdwfl

Issue 46192 in oss-fuzz: elfutils:fuzz-libdwfl: Out-of-memory in fuzz-libdwfl

[ClusterFuzz-External via monorail]

Status: New
Owner: ----
CC: elfut...@sourceware.org, da...@adalogics.com, evv...@gmail.com, izzeem@google.com 
Labels: ClusterFuzz Reproducible Engine-libfuzzer OS-Linux Proj-elfutils Reported-2022-03-30
Type: Bug

New issue 46192 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Out-of-memory in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46192

Detailed Report: https://oss-fuzz.com/testcase?key=5364854623436800

Project: elfutils
Fuzzing Engine: libFuzzer
Fuzz Target: fuzz-libdwfl
Job Type: libfuzzer_asan_elfutils
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2560 MB)
Crash Address: 
Crash State:
  fuzz-libdwfl
  
Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202203161800:202203170000

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5364854623436800

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
When you fix this bug, please
  * mention the fix revision(s).
  * state whether the bug was a short-lived regression or an old bug in any stable releases.
  * add any other useful information.
This information can help downstream consumers.

If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.

Re: Issue 46192 in oss-fuzz: elfutils:fuzz-libdwfl: Out-of-memory in fuzz-libdwfl

[Mark Wielaard]

Hi,

On Wed, Mar 30, 2022 at 03:24:17PM -0700, ClusterFuzz-External via monorail via Elfutils-devel wrote:
> New issue 46192 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Out-of-memory in fuzz-libdwfl
> https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46192
> 
> Detailed Report: https://oss-fuzz.com/testcase?key=5364854623436800
> 
> Project: elfutils
> Fuzzing Engine: libFuzzer
> Fuzz Target: fuzz-libdwfl
> Job Type: libfuzzer_asan_elfutils
> Platform Id: linux
> 
> Crash Type: Out-of-memory (exceeds 2560 MB)
> Crash Address: 
> Crash State:
>   fuzz-libdwfl
>   
> Sanitizer: address (ASAN)
> 
> Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202203161800:202203170000
> 
> Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5364854623436800

The issue with this testcase is that it has hundreds of (bad) PT_NOTE
segements. We are trying to find the build-id. For each (bogus)
PT_NOTE segement we call elf_getdata_rawchunk. There is no way to get
rid of a raw data chunk, except closing the Elf. So they just
accumulate till we run out of memory.

I don't know of a good interface to dispose of raw data chunks. But we
could mitigate this a bit by rejecting zero sized rawchunks and
searching the rawchunks to see if we already have created a chunk for
the requested offset, size and type. We currently don't keep track of
the original offset, so that would need to be tracked then.

Cheers,

Mark

Issue 46192 in oss-fuzz: elfutils:fuzz-libdwfl: Out-of-memory in fuzz-libdwfl

[ClusterFuzz-External via monorail]

Updates:
	Labels: ClusterFuzz-Verified
	Status: Verified

Comment #1 on issue 46192 by ClusterFuzz-External: elfutils:fuzz-libdwfl: Out-of-memory in fuzz-libdwfl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46192#c1

ClusterFuzz testcase 5364854623436800 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_elfutils&range=202204050601:202204051200

If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.