kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #116000
[Bug 893148] Re: CVE-2011-4132
** No longer affects: linux-lts-trusty (Ubuntu Lucid)
** No longer affects: linux-armadaxp (Ubuntu Lucid)
** No longer affects: linux-ec2 (Ubuntu Lucid)
** No longer affects: linux-goldfish (Ubuntu Lucid)
** No longer affects: linux-lts-saucy (Ubuntu Lucid)
** No longer affects: linux-lts-quantal (Ubuntu Lucid)
** No longer affects: linux-mvl-dove (Ubuntu Lucid)
** No longer affects: linux-ti-omap4 (Ubuntu Lucid)
** No longer affects: linux (Ubuntu Lucid)
** No longer affects: linux-mako (Ubuntu Lucid)
** No longer affects: linux-fsl-imx51 (Ubuntu Lucid)
** No longer affects: linux-lts-utopic (Ubuntu Lucid)
** No longer affects: linux-flo (Ubuntu Lucid)
** No longer affects: linux-lts-raring (Ubuntu Lucid)
** No longer affects: linux-manta (Ubuntu Lucid)
--
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/893148
Title:
CVE-2011-4132
Status in linux package in Ubuntu:
Fix Released
Status in linux-armadaxp package in Ubuntu:
Invalid
Status in linux-ec2 package in Ubuntu:
Invalid
Status in linux-flo package in Ubuntu:
Invalid
Status in linux-fsl-imx51 package in Ubuntu:
Invalid
Status in linux-goldfish 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-lts-saucy package in Ubuntu:
Invalid
Status in linux-lts-trusty package in Ubuntu:
Invalid
Status in linux-lts-utopic package in Ubuntu:
Invalid
Status in linux-mako package in Ubuntu:
Invalid
Status in linux-manta 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-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 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-flo source package in Precise:
Invalid
Status in linux-fsl-imx51 source package in Precise:
Invalid
Status in linux-goldfish 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-lts-saucy source package in Precise:
Invalid
Status in linux-lts-trusty source package in Precise:
Invalid
Status in linux-lts-utopic source package in Precise:
Invalid
Status in linux-mako source package in Precise:
Invalid
Status in linux-manta 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-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-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-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 source package in Trusty:
Fix Released
Status in linux-armadaxp source package in Trusty:
Invalid
Status in linux-ec2 source package in Trusty:
Invalid
Status in linux-flo source package in Trusty:
Invalid
Status in linux-fsl-imx51 source package in Trusty:
Invalid
Status in linux-goldfish 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-lts-saucy source package in Trusty:
Invalid
Status in linux-lts-trusty source package in Trusty:
Invalid
Status in linux-lts-utopic source package in Trusty:
Invalid
Status in linux-mako source package in Trusty:
Invalid
Status in linux-manta 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
Status in linux source package in Utopic:
Fix Released
Status in linux-armadaxp source package in Utopic:
Invalid
Status in linux-ec2 source package in Utopic:
Invalid
Status in linux-flo source package in Utopic:
Invalid
Status in linux-fsl-imx51 source package in Utopic:
Invalid
Status in linux-goldfish source package in Utopic:
Invalid
Status in linux-lts-backport-maverick source package in Utopic:
Invalid
Status in linux-lts-backport-natty source package in Utopic:
Invalid
Status in linux-lts-backport-oneiric source package in Utopic:
Invalid
Status in linux-lts-quantal source package in Utopic:
Invalid
Status in linux-lts-raring source package in Utopic:
Invalid
Status in linux-lts-saucy source package in Utopic:
Invalid
Status in linux-lts-trusty source package in Utopic:
Invalid
Status in linux-lts-utopic source package in Utopic:
Invalid
Status in linux-mako source package in Utopic:
Invalid
Status in linux-manta source package in Utopic:
Invalid
Status in linux-mvl-dove source package in Utopic:
Invalid
Status in linux-ti-omap4 source package in Utopic:
Invalid
Status in linux source package in Vivid:
Fix Released
Status in linux-armadaxp source package in Vivid:
Invalid
Status in linux-ec2 source package in Vivid:
Invalid
Status in linux-flo source package in Vivid:
Invalid
Status in linux-fsl-imx51 source package in Vivid:
Invalid
Status in linux-goldfish source package in Vivid:
Invalid
Status in linux-lts-backport-maverick source package in Vivid:
Invalid
Status in linux-lts-backport-natty source package in Vivid:
Invalid
Status in linux-lts-backport-oneiric source package in Vivid:
Invalid
Status in linux-lts-quantal source package in Vivid:
Invalid
Status in linux-lts-raring source package in Vivid:
Invalid
Status in linux-lts-saucy source package in Vivid:
Invalid
Status in linux-lts-trusty source package in Vivid:
Invalid
Status in linux-lts-utopic source package in Vivid:
Invalid
Status in linux-mako source package in Vivid:
Invalid
Status in linux-manta source package in Vivid:
Invalid
Status in linux-mvl-dove source package in Vivid:
Invalid
Status in linux-ti-omap4 source package in Vivid:
Invalid
Bug description:
The cleanup_journal_tail function in the Journaling Block Device (JBD)
functionality in the Linux kernel 2.6 allows local users to cause a
denial of service (assertion error and kernel oops) via an ext3 or
ext4 image with an "invalid log first block value."
Break-Fix: - 8762202dd0d6e46854f786bdb6fb3780a1625efe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/893148/+subscriptions