CVE-2016-9572

It seems like commit a817832c223 (szukw000:AFL_PATCH_0) was the final
commit created by a contributor in order to fix this issue. This
commit contains the changes in commit 7b28bd2b723 (szukw000:863-862)
which originally attempts to fix this issue. Commit a817832c223
(pull request 895 for more information) contains the changes in commit
7b28bd2b723, which fixes more than just this issue. Commit a817832c223
was never merged, however, and instead, was broken down into various
other commits by upstream, and those were merged instead. These commits
are the following: 178194c0934, 6c4e5bacb9d, 820fcfe8bb1, e03e9474667,
c5bf5ef4d65 and 16aeb9282f6, which are all referenced in pull request
895 (not merged, but the previously mentioned commits reference this
PR and therefore their links can be accessed through it). Parts of
commit a817832c223 have also been refactored and added to commit
0394f8d0f1c, which was actually merged. This commit might also contain
changes which contribute to fixing this issue. However, do note that
this last commit introduced regressions, and further changes had to
be made in order to fix those. More can be seen in pull request 975.
The patches that fix this issue are also related to CVE-2016-9580 and
CVE-2016-9581.

a non-upstream patch had previously been applied to openjpeg2

CVE-2016-{9572,9580,9581} use the same patch set CVE-2016-911{3..8} apply merge 0394f8d and commited afterwards