Threats / Android / CVE-2024-36971
CVE-2024-36971
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Android Kernel vulnerability
Android kernel contains a use-after-free vulnerability enabling remote code execution. The flaw has been observed exploited in the wild.
Verdict
Today item — known-exploited.
A use-after-free defect in the Android kernel permits remote code execution without authentication. Active exploitation in the wild confirms practical weaponization, though no ransomware campaigns have been attributed.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-08-07).
Probability (EPSS)
EPSS 0.02701 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Android, Kernel. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious input or trigger a race condition to cause the kernel to reference freed memory.
Business
Attackers gain arbitrary code execution within the kernel context, bypassing application sandboxing.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I escalate privileges by executing code at the kernel level to disable security controls.
Business
Device security model collapses; attacker gains unrestricted access to all user data and system functions.
3
Lateral reach — past segmentation narrative 3
Attacker
I persist the compromise by installing rootkits or modifying firmware to survive reboots.
Business
Compromised devices become permanently controlled infrastructure for botnet operations or espionage.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05