CVE 2016-0823
The pagemap_open function in fs/proc/task_mmu.c in the Linux kernel before 3.19.3, as used in Android 6.0.1 before 2016-03-01, allows local users to obtain sensitive physical-address information by reading a pagemap file, aka Android internal bug 25739721.
Related bugs and status
CVE-2016-0823 (Candidate) is related to these bugs:
Bug #1239087: Safely remove is not working (or broken) in Gnome Disks
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1239087 | Safely remove is not working (or broken) in Gnome Disks | gnome-disk-utility (Ubuntu) | Undecided | New | ||
Bug #1561399: CVE-2016-0823
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 1561399 | CVE-2016-0823 | linux (Ubuntu) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-ti-omap4 (Ubuntu) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-raspi2 (Ubuntu) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux (Ubuntu Xenial) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-raspi2 (Ubuntu Xenial) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-ti-omap4 (Ubuntu Xenial) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux (Ubuntu Wily) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-raspi2 (Ubuntu Wily) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-ti-omap4 (Ubuntu Wily) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561399 | CVE-2016-0823 | linux-raspi2 (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561399 | CVE-2016-0823 | linux-ti-omap4 (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561399 | CVE-2016-0823 | linux (Ubuntu Trusty) | Medium | Fix Released | ||
| 1561399 | CVE-2016-0823 | linux-raspi2 (Ubuntu Trusty) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-ti-omap4 (Ubuntu Trusty) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux (Ubuntu Precise) | Medium | Fix Released | ||
| 1561399 | CVE-2016-0823 | linux-raspi2 (Ubuntu Precise) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-ti-omap4 (Ubuntu Precise) | Medium | Fix Released | ||
| 1561399 | CVE-2016-0823 | linux-lts-trusty (Ubuntu) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-trusty (Ubuntu Precise) | Medium | Fix Released | ||
| 1561399 | CVE-2016-0823 | linux-lts-trusty (Ubuntu Trusty) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-trusty (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561399 | CVE-2016-0823 | linux-lts-trusty (Ubuntu Wily) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-trusty (Ubuntu Xenial) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-armadaxp (Ubuntu) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-armadaxp (Ubuntu Precise) | Medium | Fix Released | ||
| 1561399 | CVE-2016-0823 | linux-armadaxp (Ubuntu Trusty) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-armadaxp (Ubuntu Vivid) | Undecided | Won't Fix | ||
| 1561399 | CVE-2016-0823 | linux-armadaxp (Ubuntu Wily) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-armadaxp (Ubuntu Xenial) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-xenial (Ubuntu) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-xenial (Ubuntu Precise) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-xenial (Ubuntu Trusty) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-xenial (Ubuntu Vivid) | Undecided | New | ||
| 1561399 | CVE-2016-0823 | linux-lts-xenial (Ubuntu Wily) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-xenial (Ubuntu Xenial) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-wily (Ubuntu) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-wily (Ubuntu Precise) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-wily (Ubuntu Trusty) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-wily (Ubuntu Vivid) | Undecided | New | ||
| 1561399 | CVE-2016-0823 | linux-lts-wily (Ubuntu Wily) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-wily (Ubuntu Xenial) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-goldfish (Ubuntu) | Medium | New | ||
| 1561399 | CVE-2016-0823 | linux-goldfish (Ubuntu Precise) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-goldfish (Ubuntu Trusty) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-goldfish (Ubuntu Vivid) | Undecided | New | ||
| 1561399 | CVE-2016-0823 | linux-goldfish (Ubuntu Wily) | Medium | New | ||
| 1561399 | CVE-2016-0823 | linux-goldfish (Ubuntu Xenial) | Medium | New | ||
| 1561399 | CVE-2016-0823 | linux-lts-saucy (Ubuntu) | Medium | Invalid | ||
| 1561399 | CVE-2016-0823 | linux-lts-saucy (Ubuntu Precise) | Medium | Invalid | ||
Bug #792085: Automatic remount of safely removed USB 3.0 drive
| Summary | In | Importance | Status | |||
|---|---|---|---|---|---|---|
| 792085 | Automatic remount of safely removed USB 3.0 drive | linux (Fedora) | Undecided | Fix Released | ||
| 792085 | Automatic remount of safely removed USB 3.0 drive | linux (openSUSE) | Medium | Fix Released | ||
| 792085 | Automatic remount of safely removed USB 3.0 drive | linux (Ubuntu) | Medium | Fix Released | ||
| 792085 | Automatic remount of safely removed USB 3.0 drive | linux (Ubuntu Yakkety) | Medium | Fix Released | ||
| 792085 | Automatic remount of safely removed USB 3.0 drive | linux (Ubuntu Xenial) | Medium | Fix Released | ||
| 792085 | Automatic remount of safely removed USB 3.0 drive | linux (Ubuntu Trusty) | Medium | Triaged | ||
See the 
CVE page on Mitre.org
for more details.
