Security update for Linux kernel
Knowledgebase
(Last modified: 31AUG2006)
solutions Security update for Linux kernel
SuSE Linux Maintenance Web (5ba747ab54f313a5bd8726ca99439c15)
kernel-iseries64
kernel-pmac64
kernel-pseries64
kernel-smp
kernel-source
kernel-syms
Product(s): SUSE CORE 9 for IBM POWER
Patch: patch-11199
Release: 20060831
Obsoletes: none
- CVE-2006-3745: A double userspace copy in a SCTP ioctl allows local attackers to overflow a buffer in the kernel, potentially allowing code execution and privilege escalation. [#199441]
- CVE-2006-4093: Local attackers were able to crash PowerPC systems with PPC970 processor using a not correctly disabled privileged instruction ("attn"). [#197810]
- CVE-2006-3468: Remote attackers able to access an NFS of a ext2 or ext3 filesystem can cause a denial of service (file system panic) via a crafted UDP packet with a V2 lookup procedure that specifies a bad file handle (inode number), which triggers an error and causes an exported directory to be remounted read-only. [#192988]
- disable reading from /proc/sys/vm/toss_page_cache_nodes [#199686]
- patches.suse/delayed-atime-3: fixed a typo [#197710]
- Enable context-dependent symlinks in OCFS2 [#195081]
- Enable watchdog on IBM x460 for i386/x86-64 [#194555]
- Fix knfsd intermittently returns ENOENT on GETATTR of valid file or directory [#193934]
- fix race on link [#191713]
- A set of NFS fixes: [#189132]
- VFS: Ensure LOOKUP_CONTINUE flag is preserved by link_path_walk()
- Optimise away an excessive GETATTR call when a file is symlinked
- Cleanup initialisation of struct nfs_fattr
- Convert cache_change_attribute into a jiffy-based value
- Make nfs_fattr record the time at which the rpc call started
- Optimise inode attribute cache updates
- Remove redundant 'verifier' argument to nfs_update_inode()
- Don't let nfs_end_data_update() clobber attribute update information
- Optimise attribute revalidation on close().
- forcedeth: fix random memory scribbling bug [#188013]
- Fix problem with /proc/scsi remove-single-device [#186236]
- Fix possible work queue corruption resulting in oops. [#183391]
- sun disk label fix: use unsigned rather than signed int for sector count. [#183366]
- Updated: Page cache locking fix [#183048]
- CKRM: Free argv stuff at exec if it has been allocated earlier [#182973]
- Fix for kernel panic during power-on sequence. [#175925]
- Updated the double completion fix for fusion driver [#172910]
- Fix race in pagevec_strip [#158289]
- Fix reiserfs latencies caused by data=ordered [#154374]
- Fixed: sysctl_overcommit_memory is set to OVERCOMMIT_NEVER [#153342]
- Fix return value for 'mt tell' ioctl [#145383]
- reiserfs: fix transaction overflowing [#145070]
- ignore multiple COMM_START_WRITE_NETDUMP_ACK packets [#138321]
- Make portmap requests 'hard' when nfs filesystem is mounted 'hard' [#95374]
First, find out which kernel package to use, for example with
rpm -qf /boot/vmlinuz
Download the kernel image fitting your setup and install it with either:
rpm -Fvh kernel-syms*.rpm kernel-default*.rpm
for the default kernel image, orrpm -Fvh kernel-syms*.rpm kernel-iseries64*.rpm
for the 64 b it iSeries kernel image, orrpm -Fvh kernel-syms*.rpm kernel-pseries64*.rpm
for the 64 b it pSeries kernel image, orrpm -Fvh kernel-syms*.rpm kernel-smp*.rpm
for the SMP kernel image, orrpm -Fvh kernel-syms*.rpm kernel-pmac64*.rpm
for the 64 bit PPC kernel image
After performing the RPM package update of your kernel package, you must execute the following commands as root to make sure that your system will start up again:
mk_initrd
lilo
Finally, reboot the system with
shutdown -r now
to load the new kernel (replace "now" with the appropriate amount of time to allow local users to cleanly log out, for example "+5" for five minutes.)
Download Source Packages
Download the source code of the patches for maintained products.
Disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.