[Java] FuzzIpcFile: Uncaught exception in java.base/java.nio.HeapByteBuffer.<init>

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

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

Crash Type: Uncaught exception
Crash Address:
Crash State:
java.base/java.nio.HeapByteBuffer.
java.base/java.nio.ByteBuffer.allocate
org.apache.arrow.vector.ipc.ArrowFileReader.readSchema

Sanitizer: address (ASAN)

Recommended Security Severity: Low

Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_arrow-java&revision=202201300605

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

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.

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-15557) / @liyafan82

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

Comienza con las instrucciones de reproducción de OSS-Fuzz y el testcase 5015797066498048; después, inspecciona org.apache.arrow.vector.ipc.ArrowFileReader.readSchema y la asignación de HeapByteBuffer en el crash stack. Reproduce el fallo localmente y rastrea el procesamiento de la entrada alrededor de la lectura del esquema. Se considera terminado cuando el testcase ya no provoca una excepción no capturada.

Escrito por el modelo de indexación a partir del texto del issue.