Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-43097 Overview
CVE-2024-43097 is an out-of-bounds write vulnerability in the resizeToAtLeast function of SkRegion.cpp, part of the Skia graphics library used by Google Android. The flaw originates from an integer overflow that causes the buffer sizing calculation to underallocate memory. A local attacker with low privileges can trigger the condition without user interaction and escalate privileges on the device. The issue affects Android 12 through Android 15 and is tracked under [CWE-787: Out-of-Bounds Write].
Critical Impact
Local privilege escalation on affected Android devices through memory corruption in the Skia rendering component, with no user interaction required.
Affected Products
- Google Android 12.0 and 12.1
- Google Android 13.0 and 14.0
- Google Android 15.0
Discovery Timeline
- 2024-12-01 - Fix published in the Android Security Bulletin December 2024
- 2025-01-03 - CVE-2024-43097 published to the National Vulnerability Database
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-43097
Vulnerability Analysis
The vulnerability resides in the resizeToAtLeast method of Skia's SkRegion class, which manages region data structures used for 2D graphics clipping and rendering. The function computes the required buffer size based on untrusted input values. When those values are large, the arithmetic wraps around an unsigned integer boundary and produces a smaller allocation than needed. Subsequent writes into the undersized buffer corrupt adjacent heap memory, which an attacker can shape to achieve local escalation of privilege.
Because Skia executes within privileged system processes that render UI surfaces and process graphical content, successful exploitation grants the attacker code execution in a higher-privileged context than the originating app. The fix is tracked in Google's Skia repository under commit 8d355fe1d0795fc30b84194b87563f75c6f8f2a7.
Root Cause
The root cause is an unchecked integer overflow during buffer size computation in resizeToAtLeast. The function multiplies or sums size parameters without validating that the result fits within the destination integer type. When the overflow occurs, the allocator returns a buffer that is too small, and later writes exceed the allocated bounds, corrupting heap metadata or adjacent objects.
Attack Vector
Exploitation requires local access and low privileges, typically from an installed application. The attacker crafts a graphical payload or region data structure that triggers the overflow in the Skia rendering path. No user interaction is required. Once the out-of-bounds write occurs, the attacker leverages the heap corruption to gain execution within the targeted system component. Refer to the vendor advisory and patch commit for the specific overflow condition and corrected sizing logic.
Detection Methods for CVE-2024-43097
Indicators of Compromise
- Unexpected crashes or SIGSEGV signals in processes that load libhwui or Skia components, particularly during rendering operations involving region clipping.
- Installed applications that invoke graphics APIs with abnormally large region or path geometry parameters.
- Logcat entries referencing SkRegion faults or heap corruption aborts from scudo or jemalloc.
Detection Strategies
- Inventory Android devices against the December 2024 security patch level and flag any device below the required patch baseline.
- Monitor mobile device management (MDM) telemetry for sideloaded applications and apps requesting unusual graphics or canvas operations.
- Correlate Android crash reports with signatures tied to Skia region handling to surface exploitation attempts.
Monitoring Recommendations
- Centralize Android crash and tombstone data to detect repeat faults in Skia components across the fleet.
- Track patch deployment progress for Android 12 through 15 devices and alert on devices stalled below the December 2024 patch level.
- Review newly installed applications for suspicious use of native graphics interfaces that could trigger the overflow.
How to Mitigate CVE-2024-43097
Immediate Actions Required
- Apply the Android security patch level 2024-12-01 or later to all affected Android 12, 12.1, 13, 14, and 15 devices.
- Restrict installation of untrusted applications and enforce installation only from vetted sources through MDM policy.
- Prioritize patching for devices used by privileged users and those with access to sensitive corporate resources.
Patch Information
Google addressed the issue in the Android Security Bulletin December 2024. The upstream Skia fix is in commit 8d355fe1d0795fc30b84194b87563f75c6f8f2a7. Downstream Linux distributions that package Skia should also apply the fix; see the Debian LTS Security Announcement for details.
Workarounds
- No vendor-supplied workaround exists; patching is the only reliable remediation.
- Reduce exposure by removing untrusted applications and disabling sideloading until the device receives the December 2024 patch level or later.
- Where OEM patches are delayed, consider isolating affected devices from sensitive data and networks.
# Verify Android security patch level on a device via adb
adb shell getprop ro.build.version.security_patch
# Expected output on patched devices: 2024-12-01 or later
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

