A vulnerability was found in gcc. There is a variable ksize storing the amount of allocated memory for the array ktypevec. ksize being zero (0) indicates that some memory must be allocated upon the first write. When more memory is needed, both ksize 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 ksize remains. Since ksize is not 0, there is no indication that new memory must be allocated when there is another write to the array. This allows a malicious attacker to write arbitrary content to 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 mingw-gcc tracking bugs for this issue:
Affects: epel-all [bug 1333389]
Comment 3Raphael Sanchez Prudencio
2017-08-08 10:57:30 UTC
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/.