CVE 2016-3156
The IPv4 implementation in the Linux kernel before 4.5.2 mishandles destruction of device objects, which allows guest OS users to cause a denial of service (host OS networking outage) by arranging for a large number of IP addresses.
Related bugs and status
CVE-2016-3156 (Candidate) is related to these bugs:
Bug #661306: dangling symlinks in linux-doc package
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 661306 | dangling symlinks in linux-doc package | linux (Ubuntu) | Undecided | Fix Released | ||
| 661306 | dangling symlinks in linux-doc package | linux (Ubuntu Utopic) | Undecided | Fix Released | ||
| 661306 | dangling symlinks in linux-doc package | linux (Ubuntu Trusty) | Undecided | Fix Released | ||
| 661306 | dangling symlinks in linux-doc package | linux (Ubuntu Precise) | Undecided | Fix Released | ||
| 661306 | dangling symlinks in linux-doc package | linux (Ubuntu Vivid) | Undecided | Fix Released | ||
| 661306 | dangling symlinks in linux-doc package | linux (Ubuntu Lucid) | Undecided | Fix Released | ||
Bug #1546694: Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565)
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1546694 | Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565) | linux (Ubuntu) | Medium | Fix Released | ||
| 1546694 | Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565) | linux (Ubuntu Xenial) | Undecided | Fix Released | ||
| 1546694 | Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565) | linux (Ubuntu Vivid) | Undecided | Fix Released | ||
| 1546694 | Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565) | linux (Ubuntu Trusty) | Undecided | Fix Released | ||
| 1546694 | Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565) | linux (Ubuntu Wily) | Undecided | Fix Released | ||
Bug #1553811: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press
Bug #1556264: [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1556264 | [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read() | linux (Ubuntu) | High | Fix Released | ||
| 1556264 | [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read() | linux (Ubuntu Wily) | High | Fix Released | ||
| 1556264 | [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read() | linux (Ubuntu Xenial) | High | Fix Released | ||
| 1556264 | [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read() | linux (Ubuntu Trusty) | High | Fix Released | ||
| 1556264 | [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read() | linux-lts-vivid (Ubuntu) | High | Fix Committed | ||
| 1556264 | [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read() | linux-lts-vivid (Ubuntu Trusty) | High | Fix Released | ||
Bug #1558847: CVE-2016-3156
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1558847 | CVE-2016-3156 | linux (Ubuntu) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-ti-omap4 (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-raspi2 (Ubuntu) | Medium | New | ||
| 1558847 | CVE-2016-3156 | linux (Ubuntu Xenial) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-raspi2 (Ubuntu Xenial) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-ti-omap4 (Ubuntu Xenial) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux (Ubuntu Wily) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-raspi2 (Ubuntu Wily) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-ti-omap4 (Ubuntu Wily) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux (Ubuntu Trusty) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-raspi2 (Ubuntu Trusty) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-ti-omap4 (Ubuntu Trusty) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux (Ubuntu Precise) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-raspi2 (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-ti-omap4 (Ubuntu Precise) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-lts-trusty (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-trusty (Ubuntu Precise) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-lts-trusty (Ubuntu Trusty) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux-lts-trusty (Ubuntu Wily) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-trusty (Ubuntu Xenial) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-armadaxp (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-armadaxp (Ubuntu Precise) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-armadaxp (Ubuntu Trusty) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux-armadaxp (Ubuntu Wily) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-armadaxp (Ubuntu Xenial) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-xenial (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-xenial (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-xenial (Ubuntu Trusty) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
| 1558847 | CVE-2016-3156 | linux-lts-xenial (Ubuntu Wily) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-xenial (Ubuntu Xenial) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-wily (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-wily (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-wily (Ubuntu Trusty) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-lts-wily (Ubuntu Vivid) | Undecided | New | ||
| 1558847 | CVE-2016-3156 | linux-lts-wily (Ubuntu Wily) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-wily (Ubuntu Xenial) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-goldfish (Ubuntu) | Medium | New | ||
| 1558847 | CVE-2016-3156 | linux-goldfish (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-goldfish (Ubuntu Trusty) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-goldfish (Ubuntu Vivid) | Undecided | New | ||
| 1558847 | CVE-2016-3156 | linux-goldfish (Ubuntu Wily) | Medium | New | ||
| 1558847 | CVE-2016-3156 | linux-goldfish (Ubuntu Xenial) | Medium | New | ||
| 1558847 | CVE-2016-3156 | linux-lts-saucy (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-saucy (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-saucy (Ubuntu Trusty) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-saucy (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux-lts-saucy (Ubuntu Wily) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-saucy (Ubuntu Xenial) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-quantal (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-quantal (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-quantal (Ubuntu Trusty) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-quantal (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux-lts-quantal (Ubuntu Wily) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-quantal (Ubuntu Xenial) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-vivid (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-vivid (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-vivid (Ubuntu Trusty) | Medium | Fix Released | ||
| 1558847 | CVE-2016-3156 | linux-lts-vivid (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux-lts-vivid (Ubuntu Wily) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-vivid (Ubuntu Xenial) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-mako (Ubuntu) | Medium | New | ||
| 1558847 | CVE-2016-3156 | linux-mako (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-mako (Ubuntu Trusty) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-mako (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1558847 | CVE-2016-3156 | linux-mako (Ubuntu Wily) | Medium | New | ||
| 1558847 | CVE-2016-3156 | linux-mako (Ubuntu Xenial) | Medium | New | ||
| 1558847 | CVE-2016-3156 | linux-lts-utopic (Ubuntu) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-utopic (Ubuntu Precise) | Medium | Invalid | ||
| 1558847 | CVE-2016-3156 | linux-lts-utopic (Ubuntu Trusty) | Medium | Fix Released | ||
Bug #1561389: CVE-2016-0821
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1561389 | CVE-2016-0821 | linux (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-ti-omap4 (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-raspi2 (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-raspi2 (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-ti-omap4 (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux (Ubuntu Wily) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-raspi2 (Ubuntu Wily) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-ti-omap4 (Ubuntu Wily) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux (Ubuntu Trusty) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-raspi2 (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-ti-omap4 (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux (Ubuntu Precise) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-raspi2 (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-ti-omap4 (Ubuntu Precise) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-lts-trusty (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-trusty (Ubuntu Precise) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-lts-trusty (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux-lts-trusty (Ubuntu Wily) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-trusty (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-armadaxp (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-armadaxp (Ubuntu Precise) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-armadaxp (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux-armadaxp (Ubuntu Wily) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-armadaxp (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-xenial (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-xenial (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-xenial (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
| 1561389 | CVE-2016-0821 | linux-lts-xenial (Ubuntu Wily) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-xenial (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-wily (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-wily (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-wily (Ubuntu Trusty) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-lts-wily (Ubuntu Vivid) | Undecided | New | ||
| 1561389 | CVE-2016-0821 | linux-lts-wily (Ubuntu Wily) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-wily (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-goldfish (Ubuntu) | Medium | New | ||
| 1561389 | CVE-2016-0821 | linux-goldfish (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-goldfish (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-goldfish (Ubuntu Vivid) | Undecided | New | ||
| 1561389 | CVE-2016-0821 | linux-goldfish (Ubuntu Wily) | Medium | New | ||
| 1561389 | CVE-2016-0821 | linux-goldfish (Ubuntu Xenial) | Medium | New | ||
| 1561389 | CVE-2016-0821 | linux-lts-saucy (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-saucy (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-saucy (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-saucy (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux-lts-saucy (Ubuntu Wily) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-saucy (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-quantal (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-quantal (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-quantal (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-quantal (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux-lts-quantal (Ubuntu Wily) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-quantal (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-vivid (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-vivid (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-vivid (Ubuntu Trusty) | Medium | Fix Released | ||
| 1561389 | CVE-2016-0821 | linux-lts-vivid (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux-lts-vivid (Ubuntu Wily) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-vivid (Ubuntu Xenial) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-mako (Ubuntu) | Medium | New | ||
| 1561389 | CVE-2016-0821 | linux-mako (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-mako (Ubuntu Trusty) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-mako (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561389 | CVE-2016-0821 | linux-mako (Ubuntu Wily) | Medium | New | ||
| 1561389 | CVE-2016-0821 | linux-mako (Ubuntu Xenial) | Medium | New | ||
| 1561389 | CVE-2016-0821 | linux-lts-utopic (Ubuntu) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-utopic (Ubuntu Precise) | Medium | Invalid | ||
| 1561389 | CVE-2016-0821 | linux-lts-utopic (Ubuntu Trusty) | Medium | Fix Released | ||
Bug #1562900: Trusty update to v3.13.11-ckt37 stable release
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1562900 | Trusty update to v3.13.11-ckt37 stable release | linux (Ubuntu) | Undecided | Invalid | ||
| 1562900 | Trusty update to v3.13.11-ckt37 stable release | linux (Ubuntu Trusty) | Undecided | Fix Released | ||
Bug #1563916: CVE-2016-0774
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1563916 | CVE-2016-0774 | linux (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-ti-omap4 (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-raspi2 (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-raspi2 (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-ti-omap4 (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-raspi2 (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-ti-omap4 (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux (Ubuntu Trusty) | Medium | Fix Released | ||
| 1563916 | CVE-2016-0774 | linux-raspi2 (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-ti-omap4 (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux (Ubuntu Precise) | Medium | Fix Released | ||
| 1563916 | CVE-2016-0774 | linux-raspi2 (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-ti-omap4 (Ubuntu Precise) | Medium | Fix Released | ||
| 1563916 | CVE-2016-0774 | linux-lts-trusty (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-trusty (Ubuntu Precise) | Medium | Fix Released | ||
| 1563916 | CVE-2016-0774 | linux-lts-trusty (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux-lts-trusty (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-trusty (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-armadaxp (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-armadaxp (Ubuntu Precise) | Medium | Fix Released | ||
| 1563916 | CVE-2016-0774 | linux-armadaxp (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux-armadaxp (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-armadaxp (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-xenial (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-xenial (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-xenial (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
| 1563916 | CVE-2016-0774 | linux-lts-xenial (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-xenial (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-wily (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-wily (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-wily (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-wily (Ubuntu Vivid) | Undecided | New | ||
| 1563916 | CVE-2016-0774 | linux-lts-wily (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-wily (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-goldfish (Ubuntu) | Medium | New | ||
| 1563916 | CVE-2016-0774 | linux-goldfish (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-goldfish (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-goldfish (Ubuntu Vivid) | Undecided | New | ||
| 1563916 | CVE-2016-0774 | linux-goldfish (Ubuntu Wily) | Medium | New | ||
| 1563916 | CVE-2016-0774 | linux-goldfish (Ubuntu Xenial) | Medium | New | ||
| 1563916 | CVE-2016-0774 | linux-lts-saucy (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-saucy (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-saucy (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-saucy (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux-lts-saucy (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-saucy (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-quantal (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-quantal (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-quantal (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-quantal (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux-lts-quantal (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-quantal (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-vivid (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-vivid (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-vivid (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-vivid (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux-lts-vivid (Ubuntu Wily) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-vivid (Ubuntu Xenial) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-mako (Ubuntu) | Medium | New | ||
| 1563916 | CVE-2016-0774 | linux-mako (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-mako (Ubuntu Trusty) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-mako (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1563916 | CVE-2016-0774 | linux-mako (Ubuntu Wily) | Medium | New | ||
| 1563916 | CVE-2016-0774 | linux-mako (Ubuntu Xenial) | Medium | New | ||
| 1563916 | CVE-2016-0774 | linux-lts-utopic (Ubuntu) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-utopic (Ubuntu Precise) | Medium | Invalid | ||
| 1563916 | CVE-2016-0774 | linux-lts-utopic (Ubuntu Trusty) | Medium | Invalid | ||
Bug #1567615: Trusty update to v3.13.11-ckt38 stable release
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1567615 | Trusty update to v3.13.11-ckt38 stable release | linux (Ubuntu) | Undecided | Invalid | ||
| 1567615 | Trusty update to v3.13.11-ckt38 stable release | linux (Ubuntu Trusty) | Undecided | Fix Released | ||
Bug #1571041: Trusty update to v3.13.11-ckt39 stable release
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1571041 | Trusty update to v3.13.11-ckt39 stable release | linux (Ubuntu) | Undecided | Invalid | ||
| 1571041 | Trusty update to v3.13.11-ckt39 stable release | linux (Ubuntu Trusty) | Undecided | Fix Released | ||
Bug #1571718: linux: 3.13.0-86.130 -proposed tracker
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | linux (Ubuntu) | Medium | Invalid | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | linux (Ubuntu Trusty) | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow automated-testing | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow certification-testing | Medium | Invalid | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow prepare-package | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow prepare-package-meta | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow prepare-package-signed | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow promote-to-proposed | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow promote-to-security | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow promote-to-updates | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow regression-testing | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow security-signoff | Medium | Fix Released | ||
| 1571718 | linux: 3.13.0-86.130 -proposed tracker | Kernel SRU Workflow verification-testing | Medium | Fix Released | ||
Bug #1572261: linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | linux-lts-trusty (Ubuntu) | Medium | Invalid | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | linux-lts-trusty (Ubuntu Precise) | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow automated-testing | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow certification-testing | Medium | Invalid | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow prepare-package | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow prepare-package-meta | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow prepare-package-signed | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow promote-to-proposed | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow promote-to-security | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow promote-to-updates | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow regression-testing | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow security-signoff | Medium | Fix Released | ||
| 1572261 | linux-lts-trusty: 3.13.0-86.130~precise1 -proposed tracker | Kernel SRU Workflow verification-testing | Medium | Fix Released | ||
Bug #1572759: linux-keystone: 3.13.0-56.81 -proposed tracker
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | linux-keystone (Ubuntu) | Medium | Invalid | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow | Medium | Fix Released | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow automated-testing | Medium | Invalid | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow certification-testing | Medium | Invalid | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow prepare-package | Medium | Fix Released | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow prepare-package-meta | Medium | Fix Released | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow promote-to-proposed | Medium | Fix Released | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow promote-to-security | Medium | Fix Released | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow promote-to-updates | Medium | Fix Released | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow regression-testing | Medium | Fix Released | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow security-signoff | Medium | Invalid | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | Kernel SRU Workflow verification-testing | Medium | Fix Released | ||
| 1572759 | linux-keystone: 3.13.0-56.81 -proposed tracker | linux-keystone (Ubuntu Trusty) | Undecided | Fix Released | ||
See the 
CVE page on Mitre.org
for more details.
