#HOW TO INSTALL GLIBC 2.17 UPDATE#
Note: If your system is not connected to internet, or if you are not using the live update by connecting to a repository, then login to Red Hat support, click on Downloads, “RPM Search”, and seach for the new glibc version, and download those rpm packages manually and install it on your system.įor example, download the following RPM package for CentOS/RedHat 6 from RedHat support site, and using rpm command to install it as shown below. The above will install the following version, where this vulnerability is fixed: # rpm -qa | grep glibc # cat /etc/redhat-releaseĭo the following to fix the problem on CentOS 7.
On CentOS 7, I had the following version, which was affected by this vulnerability. In that case, do the following and then try the yum update again. Note: If you see that it is not showing the above new version, probably your yum cache should be updated. This will update the main glibc package, and the dependent glibc-common, glibc-devel and glibc-header to the latest version with the issue fixed. To fix the problem, just do the following.
On CentOS (or RedHat, or other RHEL based system), when you do yum info glibc, you’ll see the following new version with this vulnerability fixed in the “updates” repository.