CVE 2016-4805
Use-after-free vulnerability in drivers/
Related bugs and status
CVE-2016-4805 (Candidate) is related to these bugs:
Bug #1567191: CVE-2016-3951
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1567191 | CVE-2016-3951 | linux (Ubuntu) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-ti-omap4 (Ubuntu) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-raspi2 (Ubuntu) | Low | New | ||
1567191 | CVE-2016-3951 | linux (Ubuntu Xenial) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-raspi2 (Ubuntu Xenial) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-ti-omap4 (Ubuntu Xenial) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux (Ubuntu Wily) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-raspi2 (Ubuntu Wily) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-ti-omap4 (Ubuntu Wily) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux (Ubuntu Vivid) | Undecided | Fix Released | ||
1567191 | CVE-2016-3951 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1567191 | CVE-2016-3951 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1567191 | CVE-2016-3951 | linux (Ubuntu Trusty) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-raspi2 (Ubuntu Trusty) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-ti-omap4 (Ubuntu Trusty) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux (Ubuntu Precise) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-raspi2 (Ubuntu Precise) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-ti-omap4 (Ubuntu Precise) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-lts-trusty (Ubuntu) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-trusty (Ubuntu Precise) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-lts-trusty (Ubuntu Trusty) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
1567191 | CVE-2016-3951 | linux-lts-trusty (Ubuntu Wily) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-trusty (Ubuntu Xenial) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-armadaxp (Ubuntu) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-armadaxp (Ubuntu Precise) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-armadaxp (Ubuntu Trusty) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
1567191 | CVE-2016-3951 | linux-armadaxp (Ubuntu Wily) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-armadaxp (Ubuntu Xenial) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-xenial (Ubuntu) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-xenial (Ubuntu Precise) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-xenial (Ubuntu Trusty) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
1567191 | CVE-2016-3951 | linux-lts-xenial (Ubuntu Wily) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-xenial (Ubuntu Xenial) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-wily (Ubuntu) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-wily (Ubuntu Precise) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-wily (Ubuntu Trusty) | Low | Fix Released | ||
1567191 | CVE-2016-3951 | linux-lts-wily (Ubuntu Vivid) | Undecided | New | ||
1567191 | CVE-2016-3951 | linux-lts-wily (Ubuntu Wily) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-wily (Ubuntu Xenial) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-goldfish (Ubuntu) | Low | New | ||
1567191 | CVE-2016-3951 | linux-goldfish (Ubuntu Precise) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-goldfish (Ubuntu Trusty) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-goldfish (Ubuntu Vivid) | Undecided | New | ||
1567191 | CVE-2016-3951 | linux-goldfish (Ubuntu Wily) | Low | New | ||
1567191 | CVE-2016-3951 | linux-goldfish (Ubuntu Xenial) | Low | New | ||
1567191 | CVE-2016-3951 | linux-lts-saucy (Ubuntu) | Low | Invalid | ||
1567191 | CVE-2016-3951 | linux-lts-saucy (Ubuntu Precise) | Low | Invalid |
Bug #1578493: CVE-2016-4482
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1578493 | CVE-2016-4482 | linux (Ubuntu) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-ti-omap4 (Ubuntu) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-raspi2 (Ubuntu) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux (Ubuntu Yakkety) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-raspi2 (Ubuntu Yakkety) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-ti-omap4 (Ubuntu Yakkety) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux (Ubuntu Xenial) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-raspi2 (Ubuntu Xenial) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-ti-omap4 (Ubuntu Xenial) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux (Ubuntu Wily) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-raspi2 (Ubuntu Wily) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-ti-omap4 (Ubuntu Wily) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux (Ubuntu Vivid) | Undecided | Fix Released | ||
1578493 | CVE-2016-4482 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1578493 | CVE-2016-4482 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1578493 | CVE-2016-4482 | linux (Ubuntu Trusty) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-raspi2 (Ubuntu Trusty) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-ti-omap4 (Ubuntu Trusty) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux (Ubuntu Precise) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-raspi2 (Ubuntu Precise) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-ti-omap4 (Ubuntu Precise) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-lts-trusty (Ubuntu) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-trusty (Ubuntu Precise) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-lts-trusty (Ubuntu Trusty) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
1578493 | CVE-2016-4482 | linux-lts-trusty (Ubuntu Wily) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-trusty (Ubuntu Xenial) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-trusty (Ubuntu Yakkety) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-armadaxp (Ubuntu) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-armadaxp (Ubuntu Precise) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-armadaxp (Ubuntu Trusty) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
1578493 | CVE-2016-4482 | linux-armadaxp (Ubuntu Wily) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-armadaxp (Ubuntu Xenial) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-armadaxp (Ubuntu Yakkety) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-xenial (Ubuntu) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-xenial (Ubuntu Precise) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-xenial (Ubuntu Trusty) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
1578493 | CVE-2016-4482 | linux-lts-xenial (Ubuntu Wily) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-xenial (Ubuntu Xenial) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-xenial (Ubuntu Yakkety) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-wily (Ubuntu) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-wily (Ubuntu Precise) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-wily (Ubuntu Trusty) | Medium | Fix Released | ||
1578493 | CVE-2016-4482 | linux-lts-wily (Ubuntu Vivid) | Undecided | New | ||
1578493 | CVE-2016-4482 | linux-lts-wily (Ubuntu Wily) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-wily (Ubuntu Xenial) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-lts-wily (Ubuntu Yakkety) | Medium | Invalid | ||
1578493 | CVE-2016-4482 | linux-goldfish (Ubuntu) | Medium | New |
Bug #1580372: CVE-2016-4565
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1580372 | CVE-2016-4565 | linux (Ubuntu) | Medium | Fix Released | ||
1580372 | CVE-2016-4565 | linux-ti-omap4 (Ubuntu) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-raspi2 (Ubuntu) | Medium | New | ||
1580372 | CVE-2016-4565 | linux (Ubuntu Yakkety) | Medium | Won't Fix | ||
1580372 | CVE-2016-4565 | linux-raspi2 (Ubuntu Yakkety) | Medium | New | ||
1580372 | CVE-2016-4565 | linux-ti-omap4 (Ubuntu Yakkety) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux (Ubuntu Xenial) | Medium | Fix Committed | ||
1580372 | CVE-2016-4565 | linux-raspi2 (Ubuntu Xenial) | Medium | Fix Committed | ||
1580372 | CVE-2016-4565 | linux-ti-omap4 (Ubuntu Xenial) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux (Ubuntu Wily) | Medium | Fix Committed | ||
1580372 | CVE-2016-4565 | linux-raspi2 (Ubuntu Wily) | Medium | Fix Committed | ||
1580372 | CVE-2016-4565 | linux-ti-omap4 (Ubuntu Wily) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580372 | CVE-2016-4565 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580372 | CVE-2016-4565 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580372 | CVE-2016-4565 | linux (Ubuntu Trusty) | Medium | Fix Released | ||
1580372 | CVE-2016-4565 | linux-raspi2 (Ubuntu Trusty) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-ti-omap4 (Ubuntu Trusty) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux (Ubuntu Precise) | Medium | Fix Released | ||
1580372 | CVE-2016-4565 | linux-raspi2 (Ubuntu Precise) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-ti-omap4 (Ubuntu Precise) | Medium | Fix Released | ||
1580372 | CVE-2016-4565 | linux-lts-trusty (Ubuntu) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-trusty (Ubuntu Precise) | Medium | Fix Released | ||
1580372 | CVE-2016-4565 | linux-lts-trusty (Ubuntu Trusty) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580372 | CVE-2016-4565 | linux-lts-trusty (Ubuntu Wily) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-trusty (Ubuntu Xenial) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-trusty (Ubuntu Yakkety) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-armadaxp (Ubuntu) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-armadaxp (Ubuntu Precise) | Medium | Fix Released | ||
1580372 | CVE-2016-4565 | linux-armadaxp (Ubuntu Trusty) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580372 | CVE-2016-4565 | linux-armadaxp (Ubuntu Wily) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-armadaxp (Ubuntu Xenial) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-armadaxp (Ubuntu Yakkety) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-xenial (Ubuntu) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-xenial (Ubuntu Precise) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-xenial (Ubuntu Trusty) | Medium | Fix Committed | ||
1580372 | CVE-2016-4565 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
1580372 | CVE-2016-4565 | linux-lts-xenial (Ubuntu Wily) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-xenial (Ubuntu Xenial) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-xenial (Ubuntu Yakkety) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-vivid (Ubuntu) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-vivid (Ubuntu Precise) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-vivid (Ubuntu Trusty) | Medium | Fix Committed | ||
1580372 | CVE-2016-4565 | linux-lts-vivid (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580372 | CVE-2016-4565 | linux-lts-vivid (Ubuntu Wily) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-vivid (Ubuntu Xenial) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-lts-vivid (Ubuntu Yakkety) | Medium | Invalid | ||
1580372 | CVE-2016-4565 | linux-goldfish (Ubuntu) | Medium | New |
Bug #1580379: CVE-2016-4569
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1580379 | CVE-2016-4569 | linux (Ubuntu) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-ti-omap4 (Ubuntu) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-raspi2 (Ubuntu) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux (Ubuntu Yakkety) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-raspi2 (Ubuntu Yakkety) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-ti-omap4 (Ubuntu Yakkety) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux (Ubuntu Xenial) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-raspi2 (Ubuntu Xenial) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-ti-omap4 (Ubuntu Xenial) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux (Ubuntu Wily) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-raspi2 (Ubuntu Wily) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-ti-omap4 (Ubuntu Wily) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux (Ubuntu Vivid) | Undecided | Fix Released | ||
1580379 | CVE-2016-4569 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580379 | CVE-2016-4569 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580379 | CVE-2016-4569 | linux (Ubuntu Trusty) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-raspi2 (Ubuntu Trusty) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-ti-omap4 (Ubuntu Trusty) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux (Ubuntu Precise) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-raspi2 (Ubuntu Precise) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-ti-omap4 (Ubuntu Precise) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-lts-trusty (Ubuntu) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-trusty (Ubuntu Precise) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-lts-trusty (Ubuntu Trusty) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580379 | CVE-2016-4569 | linux-lts-trusty (Ubuntu Wily) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-trusty (Ubuntu Xenial) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-trusty (Ubuntu Yakkety) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-armadaxp (Ubuntu) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-armadaxp (Ubuntu Precise) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-armadaxp (Ubuntu Trusty) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580379 | CVE-2016-4569 | linux-armadaxp (Ubuntu Wily) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-armadaxp (Ubuntu Xenial) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-armadaxp (Ubuntu Yakkety) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-xenial (Ubuntu) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-xenial (Ubuntu Precise) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-xenial (Ubuntu Trusty) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
1580379 | CVE-2016-4569 | linux-lts-xenial (Ubuntu Wily) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-xenial (Ubuntu Xenial) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-xenial (Ubuntu Yakkety) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-vivid (Ubuntu) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-vivid (Ubuntu Precise) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-vivid (Ubuntu Trusty) | Low | Fix Released | ||
1580379 | CVE-2016-4569 | linux-lts-vivid (Ubuntu Vivid) | Undecided | Won't Fix | ||
1580379 | CVE-2016-4569 | linux-lts-vivid (Ubuntu Wily) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-vivid (Ubuntu Xenial) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-lts-vivid (Ubuntu Yakkety) | Low | Invalid | ||
1580379 | CVE-2016-4569 | linux-goldfish (Ubuntu) | Low | New |
Bug #1581866: CVE-2016-4578
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1581866 | CVE-2016-4578 | linux (Ubuntu) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-ti-omap4 (Ubuntu) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-raspi2 (Ubuntu) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux (Ubuntu Yakkety) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-raspi2 (Ubuntu Yakkety) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-ti-omap4 (Ubuntu Yakkety) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux (Ubuntu Xenial) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-raspi2 (Ubuntu Xenial) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-ti-omap4 (Ubuntu Xenial) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux (Ubuntu Wily) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-raspi2 (Ubuntu Wily) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-ti-omap4 (Ubuntu Wily) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux (Ubuntu Vivid) | Undecided | Fix Released | ||
1581866 | CVE-2016-4578 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1581866 | CVE-2016-4578 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1581866 | CVE-2016-4578 | linux (Ubuntu Trusty) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-raspi2 (Ubuntu Trusty) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-ti-omap4 (Ubuntu Trusty) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux (Ubuntu Precise) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-raspi2 (Ubuntu Precise) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-ti-omap4 (Ubuntu Precise) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-lts-trusty (Ubuntu) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-trusty (Ubuntu Precise) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-lts-trusty (Ubuntu Trusty) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
1581866 | CVE-2016-4578 | linux-lts-trusty (Ubuntu Wily) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-trusty (Ubuntu Xenial) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-trusty (Ubuntu Yakkety) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-armadaxp (Ubuntu) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-armadaxp (Ubuntu Precise) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-armadaxp (Ubuntu Trusty) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
1581866 | CVE-2016-4578 | linux-armadaxp (Ubuntu Wily) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-armadaxp (Ubuntu Xenial) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-armadaxp (Ubuntu Yakkety) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-xenial (Ubuntu) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-xenial (Ubuntu Precise) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-xenial (Ubuntu Trusty) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
1581866 | CVE-2016-4578 | linux-lts-xenial (Ubuntu Wily) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-xenial (Ubuntu Xenial) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-xenial (Ubuntu Yakkety) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-vivid (Ubuntu) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-vivid (Ubuntu Precise) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-vivid (Ubuntu Trusty) | Low | Fix Released | ||
1581866 | CVE-2016-4578 | linux-lts-vivid (Ubuntu Vivid) | Undecided | Won't Fix | ||
1581866 | CVE-2016-4578 | linux-lts-vivid (Ubuntu Wily) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-vivid (Ubuntu Xenial) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-lts-vivid (Ubuntu Yakkety) | Low | Invalid | ||
1581866 | CVE-2016-4578 | linux-goldfish (Ubuntu) | Low | New |
Bug #1583962: CVE-2016-4913
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1583962 | CVE-2016-4913 | linux (Ubuntu) | Low | New | ||
1583962 | CVE-2016-4913 | linux-ti-omap4 (Ubuntu) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-raspi2 (Ubuntu) | Low | New | ||
1583962 | CVE-2016-4913 | linux (Ubuntu Yakkety) | Low | Won't Fix | ||
1583962 | CVE-2016-4913 | linux-raspi2 (Ubuntu Yakkety) | Low | New | ||
1583962 | CVE-2016-4913 | linux-ti-omap4 (Ubuntu Yakkety) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux (Ubuntu Xenial) | Low | Fix Committed | ||
1583962 | CVE-2016-4913 | linux-raspi2 (Ubuntu Xenial) | Low | New | ||
1583962 | CVE-2016-4913 | linux-ti-omap4 (Ubuntu Xenial) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux (Ubuntu Wily) | Low | Fix Released | ||
1583962 | CVE-2016-4913 | linux-raspi2 (Ubuntu Wily) | Low | Fix Released | ||
1583962 | CVE-2016-4913 | linux-ti-omap4 (Ubuntu Wily) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux (Ubuntu Vivid) | Undecided | Fix Released | ||
1583962 | CVE-2016-4913 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583962 | CVE-2016-4913 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583962 | CVE-2016-4913 | linux (Ubuntu Trusty) | Low | Fix Released | ||
1583962 | CVE-2016-4913 | linux-raspi2 (Ubuntu Trusty) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-ti-omap4 (Ubuntu Trusty) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux (Ubuntu Precise) | Low | Fix Released | ||
1583962 | CVE-2016-4913 | linux-raspi2 (Ubuntu Precise) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-ti-omap4 (Ubuntu Precise) | Low | Fix Released | ||
1583962 | CVE-2016-4913 | linux-lts-trusty (Ubuntu) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-trusty (Ubuntu Precise) | Low | Fix Released | ||
1583962 | CVE-2016-4913 | linux-lts-trusty (Ubuntu Trusty) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583962 | CVE-2016-4913 | linux-lts-trusty (Ubuntu Wily) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-trusty (Ubuntu Xenial) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-trusty (Ubuntu Yakkety) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-armadaxp (Ubuntu) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-armadaxp (Ubuntu Precise) | Low | Fix Released | ||
1583962 | CVE-2016-4913 | linux-armadaxp (Ubuntu Trusty) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-armadaxp (Ubuntu Vivid) | Undecided | New | ||
1583962 | CVE-2016-4913 | linux-armadaxp (Ubuntu Wily) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-armadaxp (Ubuntu Xenial) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-armadaxp (Ubuntu Yakkety) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-xenial (Ubuntu) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-xenial (Ubuntu Precise) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-xenial (Ubuntu Trusty) | Low | New | ||
1583962 | CVE-2016-4913 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
1583962 | CVE-2016-4913 | linux-lts-xenial (Ubuntu Wily) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-xenial (Ubuntu Xenial) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-xenial (Ubuntu Yakkety) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-vivid (Ubuntu) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-vivid (Ubuntu Precise) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-vivid (Ubuntu Trusty) | Low | Fix Released | ||
1583962 | CVE-2016-4913 | linux-lts-vivid (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583962 | CVE-2016-4913 | linux-lts-vivid (Ubuntu Wily) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-vivid (Ubuntu Xenial) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-lts-vivid (Ubuntu Yakkety) | Low | Invalid | ||
1583962 | CVE-2016-4913 | linux-goldfish (Ubuntu) | Low | New |
Bug #1583963: CVE-2016-4805
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1583963 | CVE-2016-4805 | linux (Ubuntu) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-ti-omap4 (Ubuntu) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-raspi2 (Ubuntu) | Medium | New | ||
1583963 | CVE-2016-4805 | linux (Ubuntu Yakkety) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-raspi2 (Ubuntu Yakkety) | Medium | New | ||
1583963 | CVE-2016-4805 | linux-ti-omap4 (Ubuntu Yakkety) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux (Ubuntu Xenial) | Medium | Fix Committed | ||
1583963 | CVE-2016-4805 | linux-raspi2 (Ubuntu Xenial) | Medium | Fix Committed | ||
1583963 | CVE-2016-4805 | linux-ti-omap4 (Ubuntu Xenial) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux (Ubuntu Wily) | Medium | Fix Committed | ||
1583963 | CVE-2016-4805 | linux-raspi2 (Ubuntu Wily) | Medium | Fix Committed | ||
1583963 | CVE-2016-4805 | linux-ti-omap4 (Ubuntu Wily) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583963 | CVE-2016-4805 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583963 | CVE-2016-4805 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583963 | CVE-2016-4805 | linux (Ubuntu Trusty) | Medium | Fix Committed | ||
1583963 | CVE-2016-4805 | linux-raspi2 (Ubuntu Trusty) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-ti-omap4 (Ubuntu Trusty) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux (Ubuntu Precise) | Medium | Fix Released | ||
1583963 | CVE-2016-4805 | linux-raspi2 (Ubuntu Precise) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-ti-omap4 (Ubuntu Precise) | Medium | Fix Released | ||
1583963 | CVE-2016-4805 | linux-lts-trusty (Ubuntu) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-trusty (Ubuntu Precise) | Medium | Won't Fix | ||
1583963 | CVE-2016-4805 | linux-lts-trusty (Ubuntu Trusty) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583963 | CVE-2016-4805 | linux-lts-trusty (Ubuntu Wily) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-trusty (Ubuntu Xenial) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-trusty (Ubuntu Yakkety) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-armadaxp (Ubuntu) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-armadaxp (Ubuntu Precise) | Medium | Fix Released | ||
1583963 | CVE-2016-4805 | linux-armadaxp (Ubuntu Trusty) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-armadaxp (Ubuntu Vivid) | Undecided | New | ||
1583963 | CVE-2016-4805 | linux-armadaxp (Ubuntu Wily) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-armadaxp (Ubuntu Xenial) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-armadaxp (Ubuntu Yakkety) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-xenial (Ubuntu) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-xenial (Ubuntu Precise) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-xenial (Ubuntu Trusty) | Medium | Fix Committed | ||
1583963 | CVE-2016-4805 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
1583963 | CVE-2016-4805 | linux-lts-xenial (Ubuntu Wily) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-xenial (Ubuntu Xenial) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-xenial (Ubuntu Yakkety) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-vivid (Ubuntu) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-vivid (Ubuntu Precise) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-vivid (Ubuntu Trusty) | Medium | Fix Committed | ||
1583963 | CVE-2016-4805 | linux-lts-vivid (Ubuntu Vivid) | Undecided | Won't Fix | ||
1583963 | CVE-2016-4805 | linux-lts-vivid (Ubuntu Wily) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-vivid (Ubuntu Xenial) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-lts-vivid (Ubuntu Yakkety) | Medium | Invalid | ||
1583963 | CVE-2016-4805 | linux-goldfish (Ubuntu) | Medium | New |
Bug #1584890: debian.master/.../getabis bogus warnings "inconsistant compiler versions" and "not a git repository"
Bug #1585366: CVE-2016-4580
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1585366 | CVE-2016-4580 | linux (Ubuntu) | Low | New | ||
1585366 | CVE-2016-4580 | linux-ti-omap4 (Ubuntu) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-raspi2 (Ubuntu) | Low | New | ||
1585366 | CVE-2016-4580 | linux (Ubuntu Yakkety) | Low | Won't Fix | ||
1585366 | CVE-2016-4580 | linux-raspi2 (Ubuntu Yakkety) | Low | New | ||
1585366 | CVE-2016-4580 | linux-ti-omap4 (Ubuntu Yakkety) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux (Ubuntu Xenial) | Low | Fix Committed | ||
1585366 | CVE-2016-4580 | linux-raspi2 (Ubuntu Xenial) | Low | New | ||
1585366 | CVE-2016-4580 | linux-ti-omap4 (Ubuntu Xenial) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux (Ubuntu Wily) | Low | Fix Released | ||
1585366 | CVE-2016-4580 | linux-raspi2 (Ubuntu Wily) | Low | Fix Released | ||
1585366 | CVE-2016-4580 | linux-ti-omap4 (Ubuntu Wily) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux (Ubuntu Vivid) | Undecided | Fix Released | ||
1585366 | CVE-2016-4580 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1585366 | CVE-2016-4580 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
1585366 | CVE-2016-4580 | linux (Ubuntu Trusty) | Low | Fix Released | ||
1585366 | CVE-2016-4580 | linux-raspi2 (Ubuntu Trusty) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-ti-omap4 (Ubuntu Trusty) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux (Ubuntu Precise) | Low | Fix Released | ||
1585366 | CVE-2016-4580 | linux-raspi2 (Ubuntu Precise) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-ti-omap4 (Ubuntu Precise) | Low | Fix Released | ||
1585366 | CVE-2016-4580 | linux-lts-trusty (Ubuntu) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-trusty (Ubuntu Precise) | Low | Fix Released | ||
1585366 | CVE-2016-4580 | linux-lts-trusty (Ubuntu Trusty) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-trusty (Ubuntu Vivid) | Undecided | New | ||
1585366 | CVE-2016-4580 | linux-lts-trusty (Ubuntu Wily) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-trusty (Ubuntu Xenial) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-trusty (Ubuntu Yakkety) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-armadaxp (Ubuntu) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-armadaxp (Ubuntu Precise) | Low | Fix Released | ||
1585366 | CVE-2016-4580 | linux-armadaxp (Ubuntu Trusty) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-armadaxp (Ubuntu Vivid) | Undecided | New | ||
1585366 | CVE-2016-4580 | linux-armadaxp (Ubuntu Wily) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-armadaxp (Ubuntu Xenial) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-armadaxp (Ubuntu Yakkety) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-xenial (Ubuntu) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-xenial (Ubuntu Precise) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-xenial (Ubuntu Trusty) | Low | New | ||
1585366 | CVE-2016-4580 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
1585366 | CVE-2016-4580 | linux-lts-xenial (Ubuntu Wily) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-xenial (Ubuntu Xenial) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-xenial (Ubuntu Yakkety) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-vivid (Ubuntu) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-vivid (Ubuntu Precise) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-vivid (Ubuntu Trusty) | Low | Fix Released | ||
1585366 | CVE-2016-4580 | linux-lts-vivid (Ubuntu Vivid) | Undecided | New | ||
1585366 | CVE-2016-4580 | linux-lts-vivid (Ubuntu Wily) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-vivid (Ubuntu Xenial) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-lts-vivid (Ubuntu Yakkety) | Low | Invalid | ||
1585366 | CVE-2016-4580 | linux-goldfish (Ubuntu) | Low | New |
Bug #1591329: linux: 3.2.0-105.146 -proposed tracker
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1591329 | linux: 3.2.0-105.146 -proposed tracker | linux (Ubuntu) | Undecided | Invalid | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | linux (Ubuntu Precise) | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow automated-testing | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow certification-testing | Medium | Invalid | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow prepare-package | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow prepare-package-lbm | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow prepare-package-meta | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow promote-to-proposed | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow promote-to-security | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow promote-to-updates | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow regression-testing | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow security-signoff | Medium | Fix Released | ||
1591329 | linux: 3.2.0-105.146 -proposed tracker | Kernel SRU Workflow verification-testing | Medium | Fix Released |
Bug #1591435: linux-ti-omap4: 3.2.0-1483.110 -proposed tracker
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | linux-ti-omap4 (Ubuntu) | Undecided | Invalid | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | linux-ti-omap4 (Ubuntu Precise) | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow automated-testing | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow certification-testing | Medium | Invalid | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow prepare-package | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow prepare-package-meta | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow promote-to-proposed | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow promote-to-security | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow promote-to-updates | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow regression-testing | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow security-signoff | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow upload-to-ppa | Medium | Fix Released | ||
1591435 | linux-ti-omap4: 3.2.0-1483.110 -proposed tracker | Kernel SRU Workflow verification-testing | Medium | Fix Released |
Bug #1591436: linux-armadaxp: 3.2.0-1668.93 -proposed tracker
Summary | In | Importance | Status | |||
---|---|---|---|---|---|---|
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | linux-armadaxp (Ubuntu) | Undecided | Invalid | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | linux-armadaxp (Ubuntu Precise) | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow automated-testing | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow certification-testing | Medium | Invalid | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow prepare-package | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow prepare-package-meta | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow promote-to-proposed | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow promote-to-security | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow promote-to-updates | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow regression-testing | Medium | Fix Released | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow security-signoff | Medium | Invalid | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow upload-to-ppa | Medium | Invalid | ||
1591436 | linux-armadaxp: 3.2.0-1668.93 -proposed tracker | Kernel SRU Workflow verification-testing | Medium | Fix Released |
See the
CVE page on Mitre.org
for more details.