kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #23877
[Bug 894373] Re: CVE-2011-4326
** 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/894373
Title:
CVE-2011-4326
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:
Fix Released
Status in “linux-armadaxp” source package in Lucid:
Invalid
Status in “linux-ec2” source package in Lucid:
Fix Released
Status in “linux-fsl-imx51” source package in Lucid:
Invalid
Status in “linux-lts-backport-maverick” source package in Lucid:
Fix Released
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:
Fix Committed
Status in “linux-ti-omap4” source package in Lucid:
Invalid
Status in “linux” source package in Precise:
Invalid
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:
Invalid
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 udp6_ufo_fragment function in net/ipv6/udp.c in the Linux kernel
before 2.6.39, when a certain UDP Fragmentation Offload (UFO)
configuration is enabled, allows remote attackers to cause a denial of
service (system crash) by sending fragmented IPv6 UDP packets to a
bridge device.
Break-Fix: ba73542585a4a3c8a708f502e62e6e63dd74b66c
a9cf73ea7ff78f52662c8658d93c226effbbedde
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/894373/+subscriptions