Skip to main content

Android Kernel EUVDEUVD-2026-79161

| CVE-2026-55304 MEDIUM
Protection Mechanism Failure (CWE-693)
2026-09-15 Google_Devices GHSA-rhh8-4m56-73x2
6.7
CVSS 3.1 · Vendor: Google_Devices
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain System-level code execution on device
  2. Exploit
    Invoke addr_remap_address_map in remap.c
  3. Execution
    Trigger logic error in remap handling
  4. Impact
    Escalate privileges beyond System boundary

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
Exploitation Conditions

Requires the attacker to already possess System execution privileges on the device and local access to reach the vulnerable addr_remap_address_map code path in remap.c; no user interaction is needed. Limiting factors are significant: the PR:H prerequisite means the attacker must already have compromised a highly privileged context, exploitation is local-only (no network vector), and the affected component is tied to Android/Pixel builds patched in the 2026-09-01 bulletin.

Impact

This is a genuine but bounded local privilege-escalation issue, not a top-tier emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 6.7) is internally consistent with the description: exploitation is strictly local, needs no user interaction, but requires the attacker to already hold System execution privileges (PR:H) - a very high bar that already implies substantial compromise. The reward for crossing that bar (a logic error in addr_remap_address_map allowing further privilege escalation) is therefore incremental, and the C:H/I:H/A:H impacts read as generous given the attacker is already running as System. Real-world exploitation signals are all cold: EPSS is 0.12% (2nd percentile), there is no CISA KEV listing, and no public POC was identified. No SSVC decision data was supplied. Net: real defect worth patching on the normal Android/Pixel monthly cadence, but the high privilege prerequisite plus negligible exploitation-probability signals place it well below internet-facing or unauthenticated flaws. No conflict between the CVSS vector and the description - both agree the vector is local and privilege-gated.

Exploit ScenarioDerived

An attacker who has already achieved code execution in a System-privileged context on an Android/Pixel device invokes the flawed addr_remap_address_map path in remap.c and abuses the logic error to elevate beyond their current System boundary, all without any user interaction. No public exploit code was identified, so this remains a theoretical local-only chain rather than a demonstrated one.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 16, 2026

Local privilege escalation in the Android kernel's address remapping code (addr_remap_address_map in remap.c) allows an attacker who already holds System-level execution privileges to further elevate their access on the device. The flaw is a logic error in mapping validation that constitutes a protection-mechanism failure (CWE-693); successful exploitation requires local access and high privileges (CVSS:3.1/AV:L/AC:L/PR:H/UI:N), with no user interaction, and yields high confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status; EPSS is negligible at 0.12% (2nd percentile), and fixes are bundled into Google's 2026-09-01 Android/Pixel security bulletin, making this a genuine but bounded issue rather than a top-tier emergency.

RemediationAI

The primary fix is to apply the Android security patch level from Google's Pixel/Android security bulletin dated 2026-09-01 (https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01), which bundles the kernel correction for addr_remap_address_map; no standalone patch version number is published in the available data, so deployments should verify the device reports the September 2026 patch level or later (NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-55304). Because this is a local kernel flaw with a PR:H prerequisite, there is no network-facing control such as port blocking or feature toggling that meaningfully mitigates it, and disabling core kernel memory-remapping functionality is neither practical nor safe; the realistic compensating controls are reducing the likelihood that an attacker ever reaches System privilege in the first place. Operationally that means enforcing verified boot and dm-verity, keeping the System partition free of debug or engineering builds, disabling unrestricted ADB/root access (turning off USB debugging on managed devices), enforcing strong device lock credentials, and using MDM/EMM policy to restrict sideloading and privileged app installation. These controls carry trade-offs for developer and field-testing workflows but do not fully substitute for the vendor patch, since any attacker who does obtain System privileges can still exercise the flaw on an unpatched device.

Affected VersionsENISA

Android Android kernel

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerable component is the Android kernel's remap.c, specifically the addr_remap_address_map function, which manages the remapping of address ranges within the kernel address space. Address-remapping logic is inherently security-sensitive because it governs which virtual-to-physical mappings are permitted and therefore which memory a caller can reach; a logic error in this validation path means an operation that should be rejected or constrained can instead succeed. Google classifies the root cause as CWE-693 (Protection Mechanism Failure), indicating that the flaw defeats an intended memory-protection mechanism rather than being a classic buffer overflow or injection bug. The affected package is tracked by the CPE cpe:2.3:a:google:android:*:*:*:*:*:*:*:*, with EUVD describing the affected platform as the Android kernel and Google's own Pixel bulletin as the disclosure channel. Because exploitation requires the attacker to already run at System privilege, the practical risk model is a second-stage escalation from a highly privileged userspace context into stronger (kernel-level) access, and the local-only attack vector combined with the high privilege prerequisite substantially narrows the exposure surface.

Know when Android gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Google_Devices) PRIMARY 6.7 MEDIUM
AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 6.7 MEDIUM

Local logic error needing existing System privileges (AV:L/PR:H), no UI or scope change; I retain C:H/I:H/A:H to match the vendor though impact is generous for an already-System attacker.

3.1 AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Google_Devices).

CVSS VectorVendor: Google_Devices

Attack Vector
Local
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Sep 16, 2026 - 16:22 NVD
6.7 (MEDIUM)
CVE Published
Sep 15, 2026 - 18:33 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 15, 2026 - 18:33 cve.org
MEDIUM 6.7

DescriptionCVE.org

In addr_remap_address_map of remap.c, there is a possible escalation of privilege due to a logic error in the code. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
High
Android platform component, but fix shipped via Pixel security bulletin scope
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2015-3105 CRITICAL POC
10.0 Jun 10

Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy