CVE-2021-1048

Exp

In ep_loop_check_proc of eventpoll.c, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-204573007References: Upstream kernel

Published: 2021-12-15 Last update: 2025-10-23 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2021-1048 is rated Active Exploitation (77.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.05%). Core evidence: CISA KEV confirms active exploitation (added 2022-05-23) affecting Android / Kernel. a weakness (CWE-416) Unauthenticated remote administrative access may be possible. Mandatory action: The CISA remediation deadline has passed—treat as an emergency patch priority.

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

CISA KEV Record for CVE-2021-1048

Name: Android Kernel Use-After-Free Vulnerability · CISA KEV detail

Exploit added: 2022-05-23

Action due: 2022-06-13

Required action: Apply updates per vendor instructions.

Exploit prediction scoring system (EPSS) score for CVE-2021-1048

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.91% 1.05% +0.14%
2 2026-06-01 0.79% 0.91% +0.13%
3 2026-05-31 0.79%

Full EPSS history (20 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-1048

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 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:L)
A normal user session is enough; they don’t have to be admin.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 5.9 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 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:L)
A normal user session is enough; they don’t have to be admin.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
7.2 2.0 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C 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:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
3.9 10.0 [email protected]

Weakness enumeration for CVE-2021-1048

OS Trackers for CVE-2021-1048

vendor priority summary link
debian not yet assigned CVE-2021-1048 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-2021-1048
redhat high https://access.redhat.com/security/cve/CVE-2021-1048
suse high CVE-2021-1048 severity important: SUSE including 14 source package names (kernel-default, kernel-default-base, …), 233 product×package rows across 54 product lines (HPE Helion OpenStack 8, SUSE CaaS Platform 4.0, … (54 product lines)): Known Not Affected 233. https://www.suse.com/security/cve/CVE-2021-1048/
ubuntu high CVE-2021-1048 high priority: Ubuntu including 135 source packages (linux, linux-allwinner, …), 1540 status rows across 13 suites (bionic, focal, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, trusty, upstream, xenial): DNE 1154, not-affected 203, released 132, ignored 51. https://ubuntu.com/security/CVE-2021-1048

Affected software / configurations for CVE-2021-1048

Vendor Product Version Raw CPE
google android cpe:2.3:o:google:android:-:*:*:*:*:*:*:*

References for CVE-2021-1048

cvelogic Threat Intelligence