Red Hat Bugzilla – Bug 1333330
CVE-2016-4487 gcc: Invalid write due to a use-after-free to array btypevec
Last modified: 2017-08-08 07:54:51 EDT
A vulnerability was found in gcc. There is a variable bsize storing the amount of allocated memory for the array btypevec. bsize being zero (0) indicates that some memory must be allocated upon the first write. When more memory is needed, both bsize and the memory are doubled during reallocation. At some point the memory for the array is freed (in squangle_mop_up) but the value of bsize remains. Since bsize is not 0, there is no indication that new memory must be allocated when there is another write to the array. This results in NULL being written to the freed memory. External references: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70481 Upstream fix: https://gcc.gnu.org/ml/gcc-patches/2016-03/msg01687.html
Created msp430-gcc tracking bugs for this issue: Affects: fedora-all [bug 1333388]
Created mingw-gcc tracking bugs for this issue: Affects: epel-all [bug 1333389]
Statement: Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.