From: Marcelo Tosatti <marcelo@kvack.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.33-pre3
Date: Mon, 1 May 2006 04:07:40 -0300 [thread overview]
Message-ID: <20060501070740.GA28087@dmt> (raw)
Hi,
After a long time, here comes the third -pre of v2.4.33.
Mostly security related fixes, as usual.
Note: The mprotect issue, ID CVE-2006-1524, has changed to
CVE-2006-2071.
Summary of changes from v2.4.33-pre2 to v2.4.33-pre3
============================================
Andi Kleen:
x86_64: Check for bad elf entry address.
Always check that RIPs are canonical during signal handling
x86-64: Always check that RIPs are canonical during signal handling (update)
i386/x86-64: Fix x87 information leak between processes
Craig Brind:
via-rhine: zero pad short packets on Rhine I ethernet cards
David S. Miller:
ip_queue: Fix wrong skb->len == nlmsg_len assumption
Hugh Dickins:
fix shm mprotect (CVE-2006-1524)
Jeff Layton:
2.4 nfs cache consistency problem with mmap'ed files
Jesse Brandeburg:
build fix: auto_fs4 changes broke ppc64 build
Marcelo Tosatti:
Merge http://w.ods.org/kernel/2.4/linux-2.4-upstream
Change VERSION to v2.4.33-pre3
Fix printk length modifier of NFS mmap consistency patch
Marek Szuba:
quota_v2 module taints the kernel (missing licence)
Marin Mitov:
DRM: drm_stub_open() range checking
Mika Kukkonen:
VLAN: Add two missing checks to vlan_ioctl_handler()
Pavel Kankovsky:
Fix small information leak in SO_ORIGINAL_DST and getname()
Stefan-W. Hahn:
Corrected faulty syntax in drivers/input/Config.in
Stephen Rothwell:
PPC64: fix sys_rt_sigreturn() return type
Willy TARREAU:
e1000: Fix mii-tool access to setting speed and duplex
reply other threads:[~2006-05-01 7:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060501070740.GA28087@dmt \
--to=marcelo@kvack.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.