CVE-2015-8777

lowpriority · track · 22EPSS 0.006 · 47 %ileDEEUUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

0.57% (47th) EPSS

CVSS 2.1 · low

Is it mine?

142 products

Check your exposure

Who says so?

5 sources

cnnvd · enisa_euvd · cert_bund · nvd

EPSS · scored 2026-10-27

The process_envvars function in elf/rtld.c in the GNU C Library (aka glibc or libc6) before 2.23 allows local users to bypass a pointer-guarding protection mechanism via a zero value of the LD_POINTER_GUARD environment variable.

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

Fixedglibc-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.src as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-common-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-common-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-common-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-common-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-devel-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-headers-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-headers-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-headers-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-headers-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-headers-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-headers-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-headers-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-headers-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-static-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-utils-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-utils-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-utils-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-utils-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-utils-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-utils-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-utils-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixedglibc-utils-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixednscd-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixednscd-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixednscd-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixednscd-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixednscd-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixednscd-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixednscd-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Fixednscd-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all services linked to the glibc library must be restarted, or the system rebooted.
https://access.redhat.com/errata/RHSA-2017:1916
Workaroundglibc-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.src as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-common-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-common-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-common-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-common-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-debuginfo-common-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-devel-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-headers-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-headers-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-headers-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-headers-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-headers-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-headers-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-headers-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-headers-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-static-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation Optional (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-utils-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-utils-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-utils-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-utils-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-utils-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-utils-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-utils-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundglibc-utils-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundnscd-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundnscd-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundnscd-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundnscd-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundnscd-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundnscd-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundnscd-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.
Workaroundnscd-0:2.17-196.el7.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
The glibc pointer guard is a post-exploitation mitigation mechanism. As such, it is only relevant if there are exploitable security vulnerabilities in the system. Therefore, applying available security updates to the system is a possible mitigation for this issue. In typical deployments, environment variables can only be set by users with shell access. Restricting shell access to trusted users is another possible mitigation.

cvss

Technical severity, 0–10. One row per scoring source.

7.0

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–high · 2.1–7

v2.02.1lowAV:L/AC:L/Au:N/C:N/I:P/A:Nprimary · NVD / NIST USexploitability 3.9 · impact 2.9

v3.05.5mediumCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:Nprimary · NVD / NIST USexploitability 1.8 · impact 3.6

v2.03.7lowAV:L/AC:H/Au:N/C:P/I:P/A:Psecondary · Red Hat Product Security US

v3.05.1mediumCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N/E:Usecondary · CVSS-BT (t0sche)

v3.07highCVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:Hsecondary · Red Hat Product Security US

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-254USprimary

affected products (142)

Products and version ranges known to be affected.

F5 ARXall versionscert_bundDEcpe:/a:f5:arx:-
F5 BIG-IPall versionscert_bundDEcpe:/a:f5:big-ip:-
IBM BladeCenterall versionscert_bundDEcpe:/h:ibm:bladecenter:-
Oracle Linuxall versionscert_bundDEcpe:/o:oracle:linux:-
Red Hat Enterprise Linuxall versionscert_bundDEcpe:/o:redhat:enterprise_linux:-
SUSE Linux Enterprise Desktopall versionscert_bundDEcpe:/o:suse:linux_enterprise_desktop:-
SUSE Linux Enterprise Serverall versionscert_bundDEcpe:/o:suse:linux_enterprise_server:-
Ubuntu Linuxall versionscert_bundDEcpe:/o:canonical:ubuntu_linux:-
n/a n/a≤ n/aenisa_euvdEU
gnu glibc≤ 2.22nvdUScpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*
glibc-0:2.17-196.el7.aarch64 as a component of Red Hat Enterprise Linux Server (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Client (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux ComputeNode (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Server (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.i686 as a component of Red Hat Enterprise Linux Workstation (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.ppc as a component of Red Hat Enterprise Linux Server (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.s390 as a component of Red Hat Enterprise Linux Server (v. 7)all versionsfixedredhat_csafUS
glibc-0:2.17-196.el7.s390x as a component of Red Hat Enterprise Linux Server (v. 7)all versionsfixedredhat_csafUS

showing 20 of 142

advisories (2)

Vendor and ecosystem advisories describing this.

RHSA-2017:1916Red Hat Security Advisory: glibc security, bug fix, and enhancement update2017-08-01csaf · redhat_csafUS
An update for glibc is now available for Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.
WID-SEC-W-2023-0974GNU libc: Mehrere SchwachstellenDeutsch2016-01-19csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in GNU libc ausnutzen, um beliebigen Code auszuführen, um Sicherheitsfunktionen zu umgehen, um Informationen offenzulegen oder um einen Denial of Service Zustand hervorzurufen.

also known as (3)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd cert_bund nvd redhat_csaf NVD CVE.org MITRE

published 2016-01-20modified 2026-06-17

related (800)

Related entries.

ID	severity	EPSS	exploitable	published
CVE-2024-21351US	—OT critical	27.8% (98th)	KEV	2024-02-13
Windows SmartScreen Security Feature Bypass Vulnerability
CVE-2023-36025US	high8.8OT critical	88.1% (100th)	KEV	2023-11-14
Windows SmartScreen Security Feature Bypass Vulnerability
CVE-2023-36584US	—OT critical	3.25% (88th)	KEV	2023-10-10
Windows Mark of the Web Security Feature Bypass Vulnerability
CVE-2023-32049US	—OT critical	4.16% (91st)	KEV	2023-07-11
Windows SmartScreen Security Feature Bypass Vulnerability
CVE-2023-24880US	—OT critical	78.0% (100th)	KEV	2023-03-14
Windows SmartScreen Security Feature Bypass Vulnerability

+795 more

references (34)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan