Mandriva Linux Security Advisory 2010-198 - Some vulnerabilities were discovered and corrected in the Linux 2.6 kernel. These include memory disclosure, denial of service, NULL pointer dereference and privilege escalation issues.
9b5198e025901d7e83cb9d7ed6a8a856074baa405387532a1558ef7da79896f5
Mandriva Linux Security Advisory 2010-188 - Some vulnerabilities were discovered and corrected in the Linux kernel. fs/namei.c in Linux kernel 2.6.18 through 2.6.34 does not always follow NFS automount symlinks, which allows attackers to have an unknown impact, related to LOOKUP_FOLLOW. The do_pages_move function in mm/migrate.c in the Linux kernel before 2.6.33-rc7 does not validate node values, which allows local users to read arbitrary kernel memory locations, cause a denial of service , and possibly have unspecified other impact by specifying a node that is not part of the kernel node set. Various other issues have been addressed.
dfc5f7088980acc7eae211cd33475f9083b9971445292ebf8746141eefc3a0b4
Ubuntu Security Notice 966-1 - Junjiro R. Okajima discovered that knfsd did not correctly handle strict overcommit. Chris Guo, Jukka Taimisto, and Olli Jarva discovered that SCTP did not correctly handle invalid parameters. A remote attacker could send specially crafted traffic that could crash the system, leading to a denial of service. Mario Mikocevic discovered that GFS2 did not correctly handle certain quota structures. Toshiyuki Okajima discovered that the kernel keyring did not correctly handle dead keyrings. Brad Spengler discovered that Sparc did not correctly implement non-executable stacks. This made userspace applications vulnerable to exploits that would have been otherwise blocked due to non-executable memory protections. Dan Rosenberg discovered that the btrfs clone function did not correctly validate permissions. Dan Rosenberg discovered that GFS2 set_flags function did not correctly validate permissions. Shi Weihua discovered that btrfs xattr_set_acl function did not correctly validate permissions. Andre Osterhues discovered that eCryptfs did not correctly calculate hash values.
e14c23e730862eaa5b43bdf36f4764a5c6a580726d1a6ec790a50f45076c08b7