kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #24060
[Bug 1002505] Re: CVE-2012-2375
** Also affects: linux (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-fsl-imx51 (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-mvl-dove (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-ec2 (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-ti-omap4 (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-lts-backport-maverick (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-lts-backport-natty (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-lts-backport-oneiric (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-armadaxp (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-lts-quantal (Ubuntu Trusty)
Importance: Medium
Status: Invalid
** Also affects: linux-lts-raring (Ubuntu Trusty)
Importance: Medium
Status: Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1002505
Title:
CVE-2012-2375
Status in “linux” package in Ubuntu:
Invalid
Status in “linux-armadaxp” package in Ubuntu:
Invalid
Status in “linux-ec2” package in Ubuntu:
Invalid
Status in “linux-fsl-imx51” package in Ubuntu:
Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
Invalid
Status in “linux-lts-backport-natty” package in Ubuntu:
Invalid
Status in “linux-lts-backport-oneiric” package in Ubuntu:
Invalid
Status in “linux-lts-quantal” package in Ubuntu:
Invalid
Status in “linux-lts-raring” package in Ubuntu:
Invalid
Status in “linux-mvl-dove” package in Ubuntu:
Invalid
Status in “linux-ti-omap4” package in Ubuntu:
Invalid
Status in “linux” source package in Lucid:
New
Status in “linux-armadaxp” source package in Lucid:
Invalid
Status in “linux-ec2” source package in Lucid:
New
Status in “linux-fsl-imx51” source package in Lucid:
Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
Invalid
Status in “linux-lts-backport-natty” source package in Lucid:
Fix Released
Status in “linux-lts-backport-oneiric” source package in Lucid:
Fix Released
Status in “linux-lts-quantal” source package in Lucid:
Invalid
Status in “linux-lts-raring” source package in Lucid:
Invalid
Status in “linux-mvl-dove” source package in Lucid:
Invalid
Status in “linux-ti-omap4” source package in Lucid:
Invalid
Status in “linux” source package in Precise:
Fix Released
Status in “linux-armadaxp” source package in Precise:
Fix Released
Status in “linux-ec2” source package in Precise:
Invalid
Status in “linux-fsl-imx51” source package in Precise:
Invalid
Status in “linux-lts-backport-maverick” source package in Precise:
Invalid
Status in “linux-lts-backport-natty” source package in Precise:
Invalid
Status in “linux-lts-backport-oneiric” source package in Precise:
Invalid
Status in “linux-lts-quantal” source package in Precise:
Invalid
Status in “linux-lts-raring” source package in Precise:
Invalid
Status in “linux-mvl-dove” source package in Precise:
Invalid
Status in “linux-ti-omap4” source package in Precise:
Fix Released
Status in “linux” source package in Quantal:
Invalid
Status in “linux-armadaxp” source package in Quantal:
Fix Released
Status in “linux-ec2” source package in Quantal:
Invalid
Status in “linux-fsl-imx51” source package in Quantal:
Invalid
Status in “linux-lts-backport-maverick” source package in Quantal:
Invalid
Status in “linux-lts-backport-natty” source package in Quantal:
Invalid
Status in “linux-lts-backport-oneiric” source package in Quantal:
Invalid
Status in “linux-lts-quantal” source package in Quantal:
Invalid
Status in “linux-lts-raring” source package in Quantal:
Invalid
Status in “linux-mvl-dove” source package in Quantal:
Invalid
Status in “linux-ti-omap4” source package in Quantal:
Invalid
Status in “linux” source package in Raring:
Invalid
Status in “linux-armadaxp” source package in Raring:
Invalid
Status in “linux-ec2” source package in Raring:
Invalid
Status in “linux-fsl-imx51” source package in Raring:
Invalid
Status in “linux-lts-backport-maverick” source package in Raring:
Invalid
Status in “linux-lts-backport-natty” source package in Raring:
Invalid
Status in “linux-lts-backport-oneiric” source package in Raring:
Invalid
Status in “linux-lts-quantal” source package in Raring:
Invalid
Status in “linux-lts-raring” source package in Raring:
Invalid
Status in “linux-mvl-dove” source package in Raring:
Invalid
Status in “linux-ti-omap4” source package in Raring:
Invalid
Status in “linux” source package in Saucy:
Invalid
Status in “linux-armadaxp” source package in Saucy:
Invalid
Status in “linux-ec2” source package in Saucy:
Invalid
Status in “linux-fsl-imx51” source package in Saucy:
Invalid
Status in “linux-lts-backport-maverick” source package in Saucy:
Invalid
Status in “linux-lts-backport-natty” source package in Saucy:
Invalid
Status in “linux-lts-backport-oneiric” source package in Saucy:
Invalid
Status in “linux-lts-quantal” source package in Saucy:
Invalid
Status in “linux-lts-raring” source package in Saucy:
Invalid
Status in “linux-mvl-dove” source package in Saucy:
Invalid
Status in “linux-ti-omap4” source package in Saucy:
Invalid
Status in “linux” source package in Trusty:
Invalid
Status in “linux-armadaxp” source package in Trusty:
Invalid
Status in “linux-ec2” source package in Trusty:
Invalid
Status in “linux-fsl-imx51” source package in Trusty:
Invalid
Status in “linux-lts-backport-maverick” source package in Trusty:
Invalid
Status in “linux-lts-backport-natty” source package in Trusty:
Invalid
Status in “linux-lts-backport-oneiric” source package in Trusty:
Invalid
Status in “linux-lts-quantal” source package in Trusty:
Invalid
Status in “linux-lts-raring” source package in Trusty:
Invalid
Status in “linux-mvl-dove” source package in Trusty:
Invalid
Status in “linux-ti-omap4” source package in Trusty:
Invalid
Bug description:
The __nfs4_get_acl_uncached function in fs/nfs/nfs4proc.c in the NFSv4
implementation in the Linux kernel before 3.3.2 uses an incorrect
length variable during a copy operation, which allows remote NFS
servers to cause a denial of service (OOPS) by sending an excessive
number of bitmap words in an FATTR4_ACL reply. NOTE: this
vulnerability exists because of an incomplete fix for CVE-2011-4131.
Break-Fix: - 20e0fa98b751facf9a1101edaefbc19c82616a68
Break-Fix: - 5794d21ef4639f0e33440927bb903f9598c21e92
Break-Fix: - 5a00689930ab975fdd1b37b034475017e460cf2a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1002505/+subscriptions