RHSA-2018:1374

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko

To mitigate this issue: 1) Save the following script in a 'CVE-2018-1000199.stp' file. --- probe kernel.function("ptrace_set_debugreg") { if ($n < 4) $n = 4; /* set invalid debug register #, returns -EIO */ } probe begin { printk(0, "CVE-2018-1000199 mitigation loaded") } probe end { printk(0, "CVE-2018-1000199 mitigation unloaded") } --- 2) Install systemtap package and its dependencies # yum install -y systemtap systemtap-runtime # yum install -y kernel-devel kernel-debuginfo kernel-debuginfo-common 3) Build the mitigation kernel module as root. # stap -r `uname -r` -m cve_2018_1000199.ko -g CVE-2018-1000199.stp -p4 4) Load the mitigation module as root # staprun -L cve_2018_1000199.ko