apache / apache/arrow-java

[Java] FuzzIpcStream: Uncaught exception in java.base/java.nio.Bits.reserveMemory

Open
#353 0 comments 0 reactions 0 assignees View on GitHub
Type: bug
Dominant language
Java
Stars
94
Forks
152
Avg merge
3d 16h
Merged PRs (30d)
11

Description

Detailed Report:

Project: arrow-java
Fuzzing Engine: libFuzzer
Fuzz Target: FuzzIpcStream
Job Type: libfuzzer_asan_arrow-java
Platform Id: linux

Crash Type: Uncaught exception
Crash Address:
Crash State:
java.base/java.nio.Bits.reserveMemory
java.base/java.nio.DirectByteBuffer.
java.base/java.nio.ByteBuffer.allocateDirect

Sanitizer: address (ASAN)

Recommended Security Severity: Low

Crash Revision:

Reproducer Testcase:

Issue filed automatically.

See 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 . Comments on individual Monorail issues are not monitored.

This bug is subject to a 90 day disclosure deadline. If 90 days elapse
without an upstream patch, then the bug report will automatically
become visible to the public.

**Reporter**: [Liya Fan](https://issues.apache.org/jira/browse/ARROW-15562) / @liyafan82

**Note**: *This issue was originally created as [ARROW-15562](https://issues.apache.org/jira/browse/ARROW-15562). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*

Contributor guide

Open the contributing guide

Research direction

Start by reproducing testcase 4599882936090624 with the FuzzIpcStream target, following the linked OSS-Fuzz reproduction instructions. Trace the java.nio.Bits.reserveMemory and ByteBuffer.allocateDirect failure, then verify that the testcase no longer produces an uncaught exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
data-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.