Skip to main content

Android Kernel EUVDEUVD-2026-78962

| CVE-2026-56914 HIGH
Use After Free (CWE-416)
2026-09-15 Google_Devices GHSA-xm68-37r6-qfqq
8.4
CVSS 3.1 · Vendor: Google_Devices
Share

Severity by source

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

Local unprivileged app triggers a kernel UAF with no interaction; kernel-space compromise supports C/I/A:H, though a race arguably justifies AC:H.

3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/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
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

8
Analysis Updated
Sep 16, 2026 - 17:41 vuln.today
v2 (cvss_changed)
Metadata Corrected
Sep 16, 2026 - 17:40 vuln.today
tag: Android added
Re-analysis Queued
Sep 16, 2026 - 17:22 vuln.today
cvss_changed
CVSS changed
Sep 16, 2026 - 17:22 NVD
7.8 (HIGH) 8.4 (HIGH)
Analysis Generated
Sep 16, 2026 - 16:50 vuln.today
CVSS changed
Sep 16, 2026 - 16:22 NVD
7.8 (HIGH)
CVE Published
Sep 15, 2026 - 18:33 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 15, 2026 - 18:33 cve.org
HIGH 7.8

DescriptionCVE.org

In multiple locations, there is a possible use-after-free due to improper locking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

AnalysisAI

Local privilege escalation in the Android kernel affecting Google/Pixel devices lets an unprivileged app already running on the device trigger a use-after-free and gain elevated privileges. The flaw stems from improper locking in a kernel code path (CWE-416), and no user interaction is required; however, an attacker must first have local code execution on the device and must win a locking race to corrupt kernel memory, which adds real-world reliability constraints. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Requires the attacker to already have local code execution on the device as an unprivileged app (AV:L, PR:N means no elevated privileges, but on-device presence is required). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment This is a genuine but not urgent local privilege-escalation issue. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Fix by updating affected Google/Pixel devices to the Android/Pixel security patch level of 2026-09-01 or later, as documented in the vendor bulletin at https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01; there is no application-layer workaround because the defect is in the kernel itself, so an OTA firmware update is the only complete remedy. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, confirm the affected population by identifying Google/Pixel devices in the fleet and determining which are running kernel builds older than the 2026-09-01 patch level, and remind users to install pending Android security updates at the earliest opportunity since no dedicated vendor fix for this CVE is yet available. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

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

Share

EUVD-2026-78962 vulnerability details – vuln.today

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