{"id":30481,"date":"2025-04-10T19:41:25","date_gmt":"2025-04-10T19:41:25","guid":{"rendered":"https:\/\/gridinsoft.com\/blogs\/?p=30481"},"modified":"2025-04-10T19:41:25","modified_gmt":"2025-04-10T19:41:25","slug":"two-android-zero-day-vulnerabilities-fix","status":"publish","type":"post","link":"https:\/\/gridinsoft.com\/blogs\/two-android-zero-day-vulnerabilities-fix\/","title":{"rendered":"Google Releases Two Android Zero-Day Fixes, Exploited in the Wild"},"content":{"rendered":"

Google addressed two critical Android zero-day vulnerabilities in Android<\/strong>, identified as CVE-2024-53150 and CVE-2024-53197, through the April 2025 security update. These vulnerabilities were actively exploited, meaning attackers used them in real-world scenarios before the patch.<\/p>\n

Google Releases Fixes for Two Android Zero-Day Flaws<\/h2>\n

On April 8, 2025, Google released its monthly Android security bulletin<\/a>, patching 62 vulnerabilities, with a focus on two zero-day flaws<\/a> that were under active exploitation. Zero-day vulnerabilities are particularly concerning as they are exploited before developers can identify and patch them, often by sophisticated actors such as government agencies or cybercriminals. The timing of this update, aligning with the first Monday of April, follows Google’s standard practice, as noted in Android Security Bulletins Overview.<\/p>\n

The vulnerabilities, tracked as CVE-2024-53150 and CVE-2024-53197<\/strong>, were part of the Linux kernel’s USB-audio driver, a critical component handling audio over USB connections. This location in the kernel makes them especially dangerous, as kernel-level exploits can bypass many security layers, potentially leading to full device compromise. As Android itself is a derivative of Linux, such flaws touch it as well.<\/p>\n

New Android Vulnerabilities: Key Facts<\/h2>\n

To understand these vulnerabilities<\/a>, we looked into the National Vulnerability Database (NVD) and related reports. Here’s a breakdown of each issue, including technical details and potential impact.<\/p>\n

\n\n\n\n\n\n\n
<\/td>\nCVE-2024-53150<\/strong><\/td>\nCVE-2024-53197<\/strong><\/td>\n<\/tr>\n
Date of Discovery<\/td>\nLate 2024<\/td>\nLate 2024<\/td>\n<\/tr>\n
Fix Date<\/td>\nApril 8, 2025<\/td>\nApril 8, 2025<\/td>\n<\/tr>\n
What Causes<\/td>\nOut-of-bounds read in USB-audio driver due to insufficient length checks on clock descriptors<\/td>\nOut-of-bounds write in USB-audio driver due to improper bounds checking on bNumConfigurations<\/td>\n<\/tr>\n
Vulnerable Versions<\/td>\nAndroid versions prior to April 2025 patch (e.g., 12, 13, 14, 15) with unpatched Linux kernel<\/td>\nAndroid versions prior to April 2025 patch (e.g., 12, 13, 14, 15) with unpatched Linux kernel<\/td>\n<\/tr>\n<\/table>\n<\/div>\n

The first one, CVE-2024-53150<\/a>, is an out-of-bounds read in the USB-audio driver, specifically in the ALSA (Advanced Linux Sound Architecture) component of the Linux kernel. Its CVSS score is 7.8, so it\u2019s considered high severity. The problem occurs when the driver traverses clock descriptors\u2014it doesn\u2019t properly check the length (bLength) of each descriptor<\/strong>. A malicious device can exploit this by sending a bogus descriptor that\u2019s too short, causing the driver to read beyond the allocated memory.<\/p>\n

According to the vulnerability list entry, this was fixed by adding sanity checks to the validator functions to skip descriptors that don\u2019t meet the minimum length requirements. Out-of-bounds reads can leak sensitive memory data<\/a>, including user info or system-level secrets. This type of attack would typically be launched through a malicious USB device. Although there aren\u2019t many details on real-world exploitation, reports indicate it\u2019s been used in targeted attacks\u2014likely alongside other bugs for greater effect.<\/p>\n

The second vulnerability, CVE-2024-53197<\/a>, is an out-of-bounds write\u2014again in the USB-audio driver. Like the previous CVE, this one also scores a 7.8 on the CVSS scale, and worse\u2014it’s a zero-click exploit. This one involves handling certain devices like the Extigy and Mbox. Here, an attacker can manipulate the bNumConfigurations value to exceed what the driver expects. That leads to out-of-bounds writes during configuration allocation.<\/p>\n

The issue was patched by implementing proper bounds checks in the usb_get_configuration function. This flaw can be used for privilege escalation<\/strong>, potentially letting attackers inject and run arbitrary code in the kernel\u2014yes, with full system privileges. No user interaction is required.<\/p>\n

Amnesty International reported that this Android zero-day vulnerability<\/a> was part of a real-world exploit chain used by Serbian authorities in December 2024. The target? A student activist\u2019s Android phone<\/strong>. But more on that next. The exploit chain included this CVE along with CVE-2024-53104 and CVE-2024-50302, both of which had been patched earlier. This points to a coordinated attack likely involving commercial surveillance tools, such as those provided by Cellebrite.<\/p>\n

Real-World Exploitation and Targeted Attacks Suggested<\/h2>\n

Some reports confirm that both Android zero-day vulnerabilities were used in “limited, targeted exploitation,” likely by state actors or advanced persistent threat groups. The case of the Serbian student activist is particularly notable, where local authorities used these flaws to attempt spyware installation, highlighting the geopolitical implications of such vulnerabilities.<\/p>\n

So, government-backed actors are leveraging these flaws for surveillance\u2014adding a layer of complexity, especially for activists and journalists who may be targeted. It also raises questions about the role of forensic tool providers like Cellebrite, which was implicated in developing the exploit chain, leading to their banning Serbia from using their products, as noted in Candid Technology.<\/p>\n

From a technical standpoint, both Android zero-day vulnerabilities highlight the challenges of securing kernel-level components, particularly those interfacing with hardware like USB. The USB-audio driver’s complexity, handling various device types, makes it a frequent target, as seen with previous vulnerabilities like CVE-2024-53104, patched in February 2025. Policy-wise, the exploitation by state actors raises concerns about digital rights and privacy, especially in authoritarian contexts.<\/p>\n

Mitigation and User Guidance<\/h2>\n

Google acted quickly in response to these vulnerabilities, releasing patches as part of the April 2025 security update. Devices that have been updated to this patch level are protected. The update includes two patch levels: 2025-04-01 and 2025-04-05.<\/p>\n

To stay safe, users are strongly encouraged to take a few important steps. First, check for and install the latest security updates on your Android device. Make sure your patch level is 2025-04-05 or later<\/strong> to ensure you’re covered.<\/p>\n

Second, be extra cautious with USB connections<\/strong> \u2014 especially when plugging into unfamiliar or untrusted devices. These Android zero-day vulnerabilities are tied to the USB stack, so it’s not the best time to be adventurous with random charging stations.<\/p>\n","protected":false},"excerpt":{"rendered":"

Google addressed two critical Android zero-day vulnerabilities in Android, identified as CVE-2024-53150 and CVE-2024-53197, through the April 2025 security update. These vulnerabilities were actively exploited, meaning attackers used them in real-world scenarios before the patch. Google Releases Fixes for Two Android Zero-Day Flaws On April 8, 2025, Google released its monthly Android security bulletin, patching […]<\/p>\n","protected":false},"author":7,"featured_media":30513,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","footnotes":""},"categories":[6,15],"tags":[114,619,374],"class_list":{"0":"post-30481","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-mobile-security","8":"category-security-news","9":"tag-android","10":"tag-cybersecurity","11":"tag-vulnerability"},"featured_image_src":"https:\/\/gridinsoft.com\/blogs\/wp-content\/uploads\/2025\/04\/GS_BLOG_Google-Patches-Two-Actively-Exploited-Android-Zero-Day-Flaws_1280x674.webp","author_info":{"display_name":"Stephanie Adlam","author_link":"https:\/\/gridinsoft.com\/blogs\/author\/adlam\/"},"_links":{"self":[{"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/posts\/30481","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/comments?post=30481"}],"version-history":[{"count":24,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/posts\/30481\/revisions"}],"predecessor-version":[{"id":30564,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/posts\/30481\/revisions\/30564"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/media\/30513"}],"wp:attachment":[{"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/media?parent=30481"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/categories?post=30481"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gridinsoft.com\/blogs\/wp-json\/wp\/v2\/tags?post=30481"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}