diff options
| author | vchoi-hdfgroup <55293060+vchoi-hdfgroup@users.noreply.github.com> | 2023-04-14 20:41:41 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-04-14 20:41:41 (GMT) |
| commit | 2b528cc651ee609bb4bc9a0c04615d7dfc47ce65 (patch) | |
| tree | c875660ee04fc61b13e7d93ccd5f320ef59bfb61 /release_docs/RELEASE.txt | |
| parent | fcb247afd39499983c5d8e4a32c1bafe8a2e2af5 (diff) | |
| download | hdf5-2b528cc651ee609bb4bc9a0c04615d7dfc47ce65.zip hdf5-2b528cc651ee609bb4bc9a0c04615d7dfc47ce65.tar.gz hdf5-2b528cc651ee609bb4bc9a0c04615d7dfc47ce65.tar.bz2 | |
Fix for github issue #2599: (#2665) (#2735)
As indicated in the description, memory leak is detected when running "./h5dump pov".
The problem is: when calling H5O__add_cont_msg() from H5O__chunk_deserialize(),
memory is allocated for cont_msg_info->msgs. Eventually, when the library tries to load
the continuation message via H5AC_protect() in H5O_protect(), error is
encountered due to illegal info in the continuation message.
Due to the error, H5O_protect() exits but the memory allocated for cont_msg_info->msgs is not freed.
When we figure out how to handle fuzzed files that we didn't generate,
a test needs to be added to run h5dump with the provided "pov" file.
Diffstat (limited to 'release_docs/RELEASE.txt')
| -rw-r--r-- | release_docs/RELEASE.txt | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt index 7b90b8a..c938ce0 100644 --- a/release_docs/RELEASE.txt +++ b/release_docs/RELEASE.txt @@ -223,6 +223,20 @@ Bug Fixes since HDF5-1.12.1 release =================================== Library ------- + + - Memory leak + + Memory leak was detected when running h5dump with "pov". The memory was allocated + via H5FL__malloc() in hdf5/src/H5FL.c + + The fuzzed file "pov" was an HDF5 file containing an illegal continuation message. + When deserializing the object header chunks for the file, memory is allocated for the + array of continuation messages (cont_msg_info->msgs) in continuation message info struct. + As error is encountered in loading the illegal message, the memory allocated for + cont_msg_info->msgs needs to be freed. + + (VC - 2023/04/11 GH-2599) + - Fixed a memory corruption issue that can occur when reading from a dataset using a hyperslab selection in the file dataspace and a point selection in the memory dataspace |