This bug was fixed in the package linux - 3.13.0-135.184
---------------
linux (3.13.0-135.184) trusty; urgency=low
* linux: 3.13.0-135.184 -proposed tracker (LP: #1724500)
* Trusty NVMe boot fails on some systems (LP: #1720867)
- NVMe: RCU protected access to io queues
- NVMe: IOCTL path RCU protect queue access
- powerpc/mm: fix ".__node_distance" undefined
- NVMe: per-cpu io queues
- nvme: Use pci_enable_msi_range() and pci_enable_msix_range()
- NVMe: make setup work for devices that don't do INTx
- NVMe: Always use MSI/MSI-x interrupts
linux (3.13.0-134.183) trusty; urgency=low
* linux: 3.13.0-134.183 -proposed tracker (LP: #1722335)
[ Thadeu Lima de Souza Cascardo ]
* CVE-2017-10661
- timerfd: Protect the might cancel mechanism proper
* CVE-2017-10662
- f2fs: sanity check segment count
* CVE-2017-10663
- f2fs: sanity check checkpoint segno and blkoff
* CVE-2017-14340
- xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present
* CVE-2017-10911
- xen-blkback: don't leak stack data via response ring
* CVE-2017-11176
- mqueue: fix a use-after-free in sys_mq_notify()
* CVE-2016-8632
- tipc: check minimum bearer MTU
-- Thadeu Lima de Souza Cascardo <casca...@canonical.com> Wed, 18 Oct
2017 07:09:04 -0200
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-8632
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10661
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10662
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10663
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-10911
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-11176
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-14340
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1724500
Title:
linux: 3.13.0-135.184 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Committed
Status in Kernel SRU Workflow promote-to-updates series:
Fix Committed
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
Invalid
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Released
Bug description:
This bug is for tracking the 3.13.0-135.184 upload package. This bug
will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: 1724562
derivatives:
-- swm properties --
boot-testing-requested: true
phase: Promoted to proposed
proposed-announcement-sent: true
proposed-testing-requested: true
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724500/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
