From ${URL} : When the parser encountered a deeply nested element with an infinite size then a following element of an upper level was not propagated correctly. Instead the element with the infinite size was added into the EBML element tree a second time resulting in memory access after freeing it and multiple attempts to free the same memory address during destruction. Upstream patch: https://github.com/Matroska-Org/libebml/commit/88409e2a94dd3b40ff81d08bf6d92f486d036b24 @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
already fixed in 1.3.3 which is good to go stable I think
Arches, please test and mark stable: =dev-libs/libebml-1.3.3 Target keywords : "alpha amd64 arm hppa ia64 ppc ppc64 sparc x86"
amd64 stable
x86 stable
Stable for HPPA PPC64.
Stable on alpha.
ppc stable
sparc stable
arm stable
ia64 stable
@maintainer(s), please cleanup.
Please clean the vulnerable versions.
GLSA Vote: No Cleanup PR: https://github.com/gentoo/gentoo/pull/3465
Tree is clean. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2f87d7ca8e04832e2b50a9b140ccd6812e7c45a8