HIGH · CVSS 7.8 CISA Known Exploited Vulnerability

CVE-2021-1048

Android Kernel Use-After-Free Vulnerability

Android Kernel

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

CVSS
7.8
HIGH
EPSS
1%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
15 Dec 2021
CWE-416

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 23 May 2022. US federal agencies were required to remediate it by 13 June 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 1%, which is higher than 61.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2021-1048 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2021-1048.

What does CVE-2021-1048 affect?

CVE-2021-1048 affects Android Kernel. 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

How severe is CVE-2021-1048?

CVE-2021-1048 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 1%, higher than 61.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 13 June 2022.

How should organisations respond to CVE-2021-1048?

Apply the vendor patch for Android Kernel as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.