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.

Published: 2016-03-12 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-0823 is rated Low Risk (24/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.30%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-0823

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.30% +0.29%
2 2025-03-30 0.06% 0.01% -0.05%
3 2025-03-29 — 0.06% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-0823

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.0 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.5 1.4 [email protected]
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 3.9 2.9 [email protected]

Weakness enumeration for CVE-2016-0823

OS Trackers for CVE-2016-0823

vendor priority summary link
debian not yet assigned CVE-2016-0823 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-0823
redhat low — https://access.redhat.com/security/cve/CVE-2016-0823
suse medium CVE-2016-0823 severity moderate: SUSE including 112 source package names (kernel-bigmem-3.0.101-88.1, kernel-bigmem-base-3.0.101-88.1, …), 434 product×package rows across 62 product lines (HPE Helion OpenStack 8, SUSE CaaS Platform 4.0, … (62 product lines)): Known Not Affected 244, Fixed 190. https://www.suse.com/security/cve/CVE-2016-0823/
ubuntu medium CVE-2016-0823 medium priority: Ubuntu including 99 source packages (linux, linux-armadaxp, …), 828 status rows across 13 suites (artful, bionic, focal, jammy, noble, plucky, precise, trusty, upstream, wily, xenial, yakkety, zesty): DNE 551, not-affected 139, released 105, ignored 33. https://ubuntu.com/security/CVE-2016-0823

Affected software / configurations for CVE-2016-0823

Vendor Product Version Raw CPE
google android 6.0.1 cpe:2.3:o:google:android:6.0.1:*:*:*:*:*:*:*
linux linux_kernel <= 3.19.2 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

References for CVE-2016-0823

cvelogic Threat Intelligence