RHSA-2008:0233High

Red Hat Security Advisory: kernel security and bug fix update

Published
May 7, 2008
Last Modified
June 25, 2026

🔗 CVE IDs covered (6)

CVE-2007-5498 →CVE-2008-0007 →CVE-2008-1367 →CVE-2008-1375 →CVE-2008-1619 →CVE-2008-1669 →

📋 Description

CVE-2007-5498 — missing sanity check in xen block backend driver CVE-2008-0007 — kernel: insufficient range checks in fault handlers with mremap CVE-2008-1367 — Kernel doesn't clear DF for signal handlers CVE-2008-1375 — kernel: race condition in dnotify (local DoS, local roothole possible) CVE-2008-1619 — [xen-ia64] Dom0 panic while we run ftp test tool between HVM and Dom0. CVE-2008-1669 — kernel: add rcu_read_lock() to fcheck() in both dnotify, locks.c and fix fcntl store/load race in locks.c

🎯 Affected products87

  • Red Hat Enterprise Linux (v. 5 server)
  • Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-0:2.6.18-53.1.19.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-0:2.6.18-53.1.19.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-0:2.6.18-53.1.19.el5.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-0:2.6.18-53.1.19.el5.src as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-0:2.6.18-53.1.19.el5.src as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-0:2.6.18-53.1.19.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-0:2.6.18-53.1.19.el5.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-PAE-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-PAE-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-PAE-debuginfo-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-PAE-debuginfo-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-PAE-devel-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-PAE-devel-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-debug-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-debug-0:2.6.18-53.1.19.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-0:2.6.18-53.1.19.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-0:2.6.18-53.1.19.el5.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-0:2.6.18-53.1.19.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-0:2.6.18-53.1.19.el5.x86_64 as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-debug-debuginfo-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-debuginfo-0:2.6.18-53.1.19.el5.i686 as a component of Red Hat Enterprise Linux Desktop (v. 5 client)
  • kernel-debug-debuginfo-0:2.6.18-53.1.19.el5.ia64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-debuginfo-0:2.6.18-53.1.19.el5.ppc64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-debuginfo-0:2.6.18-53.1.19.el5.s390x as a component of Red Hat Enterprise Linux (v. 5 server)
  • kernel-debug-debuginfo-0:2.6.18-53.1.19.el5.x86_64 as a component of Red Hat Enterprise Linux (v. 5 server)
  • +57 more not shown

✅ Remediation

Before applying this update, make sure that all previously-released errata relevant to your system have been applied. This update is available via Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at http://kbase.redhat.com/faq/FAQ_58_10188

🔗 References (16)