← Back to team overview

kernel-packages team mailing list archive

[Bug 1283101] Re: CVE-2014-0069: add hardening patch

 

** Changed in: linux (Ubuntu Lucid)
       Status: New => Confirmed

** Changed in: linux-ec2 (Ubuntu Lucid)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: linux-ti-omap4 (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: linux-lts-quantal (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: linux-lts-raring (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: linux-lts-saucy (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: linux-armadaxp (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Quantal)
       Status: New => Confirmed

** Changed in: linux-ti-omap4 (Ubuntu Quantal)
       Status: New => Confirmed

** Changed in: linux-ti-omap4 (Ubuntu Saucy)
       Status: New => Confirmed

** Changed in: linux-armadaxp (Ubuntu Quantal)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Saucy)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Trusty)
       Status: Triaged => Confirmed

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

Title:
  CVE-2014-0069: add hardening patch

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-armadaxp” package in Ubuntu:
  Invalid
Status in “linux-ec2” 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-ti-omap4” package in Ubuntu:
  Invalid
Status in “linux” source package in Lucid:
  Confirmed
Status in “linux-armadaxp” source package in Lucid:
  Invalid
Status in “linux-ec2” source package in Lucid:
  Confirmed
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-ti-omap4” source package in Lucid:
  Invalid
Status in “linux” source package in Precise:
  Confirmed
Status in “linux-armadaxp” source package in Precise:
  Confirmed
Status in “linux-ec2” source package in Precise:
  Invalid
Status in “linux-lts-quantal” source package in Precise:
  Confirmed
Status in “linux-lts-raring” source package in Precise:
  Confirmed
Status in “linux-lts-saucy” source package in Precise:
  Confirmed
Status in “linux-ti-omap4” source package in Precise:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “linux-armadaxp” source package in Quantal:
  Confirmed
Status in “linux-ec2” 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-lts-saucy” source package in Quantal:
  Invalid
Status in “linux-ti-omap4” source package in Quantal:
  Confirmed
Status in “linux” source package in Saucy:
  Confirmed
Status in “linux-armadaxp” source package in Saucy:
  Invalid
Status in “linux-ec2” 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-lts-saucy” source package in Saucy:
  Invalid
Status in “linux-ti-omap4” source package in Saucy:
  Confirmed
Status in “linux” source package in Trusty:
  Confirmed
Status in “linux-armadaxp” source package in Trusty:
  Invalid
Status in “linux-ec2” 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-ti-omap4” source package in Trusty:
  Invalid

Bug description:
  This CVE was fixed under 5d81de8e8667da7135d3a32a964087c0faf5483f but
  there is a second fix which will make this much safer going forward
  against other bugs:

      http://article.gmane.org/gmane.linux.kernel.cifs/9402

  Makes sense to put this into any release which needs it.

  # from cifs branch for-next (may change again yet)
  Break-fix: - a26054d184763969a411e3939fe243516715ff59

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


References