OCaml versions 4.02.3 and earlier have a runtime bug that, on 64-bit platforms, causes sizes arguments to an internal memmove call to be sign-extended from 32 to 64-bits before being passed to the memmove function. This leads arguments between 2GiB and 4GiB to be interpreted as larger than they are (specifically, a bit below 2^64), causing a buffer overflow. Arguments between 4GiB and 6GiB are interpreted as 4GiB smaller than they should be, causing a possible information leak. References: http://seclists.org/oss-sec/2016/q2/165 Upstream fix: https://github.com/ocaml/ocaml/commit/659615c7b100a89eafe6253e7a5b9d84d0e8df74#diff-a97df53e3ebc59bb457191b496c90762
Created ocaml tracking bugs for this issue: Affects: fedora-all [bug 1332091]
ocaml-4.02.3-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
ocaml-4.02.2-5.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2016:1296 https://access.redhat.com/errata/RHSA-2016:1296
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2016:2576 https://rhn.redhat.com/errata/RHSA-2016-2576.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2017:0564 https://rhn.redhat.com/errata/RHSA-2017-0564.html
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2017:0565 https://rhn.redhat.com/errata/RHSA-2017-0565.html