kernel-packages team mailing list archive

[Launchpad Bug Tracker <1362447@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package linux - 3.16.0-12.18

---------------
linux (3.16.0-12.18) utopic; urgency=low

  [ Paolo Pisati ]

  * Revert "[Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
    /boot/dtb-(uname -r) to make flash-kernel happy"
  * Revert "[Debian] dtb: don't remove a symlink dereferencing an existing
    directory"
  * Revert "[Debian] dtb: don't follow symlink when checking for a
    directory"
  * Revert "[Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb"
  * Revert "[Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)"

linux (3.16.0-12.17) utopic; urgency=low

  [ Andy Whitcroft ]

  * Release Tracking Bug
    - LP: #1363032
  * Revert "[Config] Switch kernel to vmlinuz (from vmlinux) on ppc64el"

  [ dann frazier ]

  * [Config] CONFIG_ARM_GIC_V3=y

  [ Douglas Lehr ]

  * SAUCE: (no-up) PCI: Increase BAR size quirk for IBM ipr SAS Crocodile
    adapters
    - LP: #1361364

  [ Marc Dietrich ]

  * [Config] arm/tegra/d-i: framebuffer and usb support for Tegra SoCs

  [ Paolo Pisati ]

  * [Config] armhf: REGULATOR_TWL4030=y
  * [Debian] dtb: move dtbs installation to /boot/dtb-$(uname -r)
  * [Debian] dtb: symlink from /boot/dtb-$(uname -r) to /boot/dtb
  * [Debian] dtb: don't follow symlink when checking for a directory
  * [Debian] dtb: don't remove a symlink dereferencing an existing
    directory
  * [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
    /boot/dtb-(uname -r) to make flash-kernel happy

  [ Stefan Bader ]

  * SAUCE: x86/xen: Fix setup of 64bit kernel pagetables
    - LP: #1350522

  [ Upstream Kernel Changes ]

  * drm/tegra: add MODULE_DEVICE_TABLEs
  * kvm: iommu: fix the third parameter of kvm_iommu_put_pages
    (CVE-2014-3601)
    - LP: #1362443
    - CVE-2014-3601
  * isofs: Fix unbounded recursion when processing relocated directories
    - LP: #1362447, #1362448
    - CVE-2014-5472
  * arm64/crypto: fix makefile rule for aes-glue-%.o
  * irq-gic: remove file name from heading comment
  * irqchip: gic: Move some bits of GICv2 to a library-type file
  * irqchip: gic-v3: Initial support for GICv3
  * arm64: GICv3 device tree binding documentation
  * arm64: boot protocol documentation update for GICv3
  * KVM: arm/arm64: vgic: move GICv2 registers to their own structure
  * KVM: ARM: vgic: introduce vgic_ops and LR manipulation primitives
  * KVM: ARM: vgic: abstract access to the ELRSR bitmap
  * KVM: ARM: vgic: abstract EISR bitmap access
  * KVM: ARM: vgic: abstract MISR decoding
  * KVM: ARM: vgic: move underflow handling to vgic_ops
  * KVM: ARM: vgic: abstract VMCR access
  * KVM: ARM: vgic: introduce vgic_enable
  * KVM: ARM: introduce vgic_params structure
  * KVM: ARM: vgic: split GICv2 backend from the main vgic code
  * KVM: ARM: vgic: revisit implementation of irqchip_in_kernel
  * arm64: KVM: remove __kvm_hyp_code_{start,end} from hyp.S
  * arm64: KVM: split GICv2 world switch from hyp code
  * arm64: KVM: move HCR_EL2.{IMO,FMO} manipulation into the vgic switch
    code
  * KVM: ARM: vgic: add the GICv3 backend
  * arm64: KVM: vgic: add GICv3 world switch
  * arm64: KVM: vgic: enable GICv2 emulation on top on GICv3 hardware
  * arm64: gicv3: Allow GICv3 compilation with older binutils
  * arm64: KVM: GICv3: move system register access to msr_s/mrs_s
  * KVM: arm64: GICv3: mandate page-aligned GICV region
 -- Andy Whitcroft <apw@xxxxxxxxxxxxx>   Mon, 01 Sep 2014 12:40:54 +0100

** Changed in: linux (Ubuntu Utopic)
       Status: New => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-3601

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-5472

-- 
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/1362447

Title:
  CVE-2014-5471

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-fsl-imx51” package in Ubuntu:
  Invalid
Status in “linux-lts-backport-maverick” package in Ubuntu:
  New
Status in “linux-lts-backport-natty” package in Ubuntu:
  New
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-mvl-dove” package in Ubuntu:
  Invalid
Status in “linux-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Fix Committed
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:
  New
Status in “linux-lts-backport-natty” source package in Lucid:
  New
Status in “linux-lts-quantal” source package in Lucid:
  Invalid
Status in “linux-lts-raring” source package in Lucid:
  Invalid
Status in “linux-lts-saucy” 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 Committed
Status in “linux-armadaxp” source package in Precise:
  New
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:
  New
Status in “linux-lts-backport-natty” source package in Precise:
  New
Status in “linux-lts-quantal” source package in Precise:
  New
Status in “linux-lts-raring” source package in Precise:
  New
Status in “linux-lts-saucy” source package in Precise:
  New
Status in “linux-mvl-dove” source package in Precise:
  Invalid
Status in “linux-ti-omap4” source package in Precise:
  New
Status in “linux” source package in Trusty:
  Fix Committed
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:
  New
Status in “linux-lts-backport-natty” source package in Trusty:
  New
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-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-fsl-imx51” source package in Utopic:
  Invalid
Status in “linux-lts-backport-maverick” source package in Utopic:
  New
Status in “linux-lts-backport-natty” source package in Utopic:
  New
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-mvl-dove” source package in Utopic:
  Invalid
Status in “linux-ti-omap4” source package in Utopic:
  Invalid

Bug description:
  [unbound recursion in ISOFS - crashes / reboots a kernel due to kernel
  stack overflow / corruption]

  Break-Fix: - 410dd3cf4c9b36f27ed4542ee18b1af5e68645a4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1362447/+subscriptions