CVE-2011-1093
highPriorität · verfolgen · 32EPSS 0.035 · 89. PerzentilEUUSEPSS · bewertet 2026-10-23
The dccp_rcv_state_process function in net/dccp/input.c in the Datagram Congestion Control Protocol (DCCP) implementation in the Linux kernel before 2.6.38 does not properly handle packets for a CLOSED endpoint, which allows remote attackers to cause a denial of service (NULL pointer dereference and OOPS) by sending a DCCP-Close packet followed by a DCCP-Reset packet.
Behebungen
Hersteller-Fix, Mitigation oder Workaround, wie von den Quellen veröffentlicht.
Ein Hersteller-Fix ist verfügbar.
- Behobenkernel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.src as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.src as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.src as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.src as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-bootwrapper-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debug-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-i686-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-i686-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-i686-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-ppc64-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-s390x-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-x86_64-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-x86_64-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-x86_64-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-debuginfo-common-x86_64-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-doc-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-doc-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-doc-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-doc-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-firmware-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-firmware-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-firmware-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-firmware-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-kdump-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-kdump-debuginfo-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-kdump-devel-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenperf-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenperf-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenperf-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenperf-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0498 - Behobenkernel-rt-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-0:2.6.33.9-rt31.64.el5rt.src as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debug-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debug-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debug-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debug-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debug-devel-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debug-devel-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debuginfo-common-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-debuginfo-common-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-devel-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-devel-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-doc-0:2.6.33.9-rt31.64.el5rt.noarch as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-trace-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-trace-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-trace-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-trace-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-trace-devel-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-trace-devel-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-vanilla-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-vanilla-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-vanilla-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-vanilla-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-vanilla-devel-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-rt-vanilla-devel-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenperf-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenperf-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenperf-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenperf-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0500 - Behobenkernel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-0:2.6.18-238.12.1.el5.src as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-PAE-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-PAE-debuginfo-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-PAE-devel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-devel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-devel-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-devel-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-devel-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debug-devel-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-common-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-common-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-common-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-common-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-debuginfo-common-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-devel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-devel-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-devel-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-devel-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-devel-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-doc-0:2.6.18-238.12.1.el5.noarch as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-kdump-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-kdump-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-kdump-debuginfo-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-kdump-debuginfo-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-kdump-devel-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-kdump-devel-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-debuginfo-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-debuginfo-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-debuginfo-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-devel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-devel-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Behobenkernel-xen-devel-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
Before applying this update, make sure all previously-released errata relevant to your system have been applied. This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/kb/docs/DOC-11259 To install kernel packages manually, use "rpm -ivh [package]". Do not use "rpm -Uvh" as that will remove the running kernel binaries from your system. You may use "rpm -e" to remove old kernels after determining that the new kernel functions properly on your system.
https://access.redhat.com/errata/RHSA-2011:0833 - Workaroundkernel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.src as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.src as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.src as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.src as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-bootwrapper-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-i686-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-i686-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-i686-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-ppc64-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-s390x-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-x86_64-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-x86_64-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-x86_64-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-x86_64-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-doc-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-doc-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-doc-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-doc-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-firmware-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-firmware-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-firmware-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-firmware-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.i686 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.ppc64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.32-71.29.1.el6.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-debuginfo-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-devel-0:2.6.32-71.29.1.el6.s390x as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundperf-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Desktop (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundperf-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux HPC Node (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundperf-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Server (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundperf-0:2.6.32-71.29.1.el6.noarch as a component of Red Hat Enterprise Linux Workstation (v. 6)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-0:2.6.33.9-rt31.64.el5rt.src as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debug-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debug-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debug-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debug-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debug-devel-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debug-devel-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debuginfo-common-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-debuginfo-common-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-devel-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-devel-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-doc-0:2.6.33.9-rt31.64.el5rt.noarch as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-trace-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-trace-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-trace-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-trace-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-trace-devel-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-trace-devel-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-vanilla-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-vanilla-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-vanilla-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-vanilla-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-vanilla-devel-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-rt-vanilla-devel-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundperf-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundperf-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundperf-debuginfo-0:2.6.33.9-rt31.64.el5rt.i686 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundperf-debuginfo-0:2.6.33.9-rt31.64.el5rt.x86_64 as a component of MRG Realtime for RHEL 5 Serverredhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.18-238.12.1.el5.src as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-PAE-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-PAE-debuginfo-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-PAE-devel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-debuginfo-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debug-devel-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-debuginfo-common-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-devel-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-doc-0:2.6.18-238.12.1.el5.noarch as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.18-238.12.1.el5.i386 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.18-238.12.1.el5.ppc as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-headers-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-debuginfo-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-debuginfo-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-devel-0:2.6.18-238.12.1.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-kdump-devel-0:2.6.18-238.12.1.el5.s390x as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-debuginfo-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-debuginfo-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-debuginfo-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-devel-0:2.6.18-238.12.1.el5.i686 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-devel-0:2.6.18-238.12.1.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
- Workaroundkernel-xen-devel-0:2.6.18-238.12.1.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5.6.z server)redhat_csaf
For users that do not run applications that use DCCP, you can prevent the dccp module from being loaded by adding the following entry to the end of the /etc/modprobe.d/blacklist file: blacklist dccp This way, the dccp module cannot be loaded accidentally, which may occur if an application that requires DCCP is started. A reboot is not necessary for this change to take effect but do make sure the module is not loaded in the first place. You can verify that by running: lsmod | grep dccp You may also consider removing the CAP_SYS_MODULE capability from the current global capability set to prevent kernel modules from being loaded or unloaded. The CAP_SYS_MODULE has a capability number of 16 (see linux/capability.h). The default value has all the bits set. To remove this capability, you have to clear the 16th bit of the default 32-bit value, e.g. 0xffffff ^ (1 << 16): echo 0xFFFEFFFF > /proc/sys/kernel/cap-bound
cvss
Technischer Schweregrad, 0–10. Eine Zeile je Quelle.
Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen⚠ Quellen uneinig · medium–high · 6.6–7.8
schwächen
Die CWE-Schwächeklassen, zu denen dies gehört.
betroffene Produkte (192)
Betroffene Produkte und Versionsbereiche.
- redhat enterprise linux workstation= 5.0nvdUScpe:2.3:o:redhat:enterprise_linux_workstation:*:*:*:*:*:*:*:*
Advisories (3)
Hersteller- und Ökosystem-Meldungen dazu.
- RHSA-2011:0498Red Hat Security Advisory: kernel security, bug fix, and enhancement update2011-05-10csaf · redhat_csafUS
Updated kernel packages that fix several security issues, various bugs, and add an enhancement are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
- RHSA-2011:0500Red Hat Security Advisory: kernel-rt security and bug fix update2011-05-10csaf · redhat_csafUS
Updated kernel-rt packages that fix multiple security issues and various bugs are now available for Red Hat Enterprise MRG 1.3. The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
- RHSA-2011:0833Red Hat Security Advisory: kernel security and bug fix update2011-05-31csaf · redhat_csafUS
Updated kernel packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
auch bekannt als (3)
Weitere Namen und Kennungen dieser Entität.
quellen
Welche Quellen diesen Datensatz belegen und wann.
Referenzen (30)
Externe Belege — Patches, Meldungen, Analysen.
- http://downloads.avaya.com/css/P8/documents/100145416cnnvd
- http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=720dc34bbbe9493c7bd48b2243058b4e447a929dcnnvd
- http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=720dc34bbbe9493c7bd48b2243058b4e447a929dcnnvd
- http://openwall.com/lists/oss-security/2011/03/08/19cnnvd
- http://openwall.com/lists/oss-security/2011/03/08/4cnnvd
- http://rhn.redhat.com/errata/RHSA-2011-0833.htmlcnnvd
- http://wiki.openvz.org/Download/kernel/rhel5/028stab091.1Patchcnnvd
- http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.38cnnvd
Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan