Android's March 2026 security patch fixes over 100 flaws, one under targeted exploitation
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2024-43859 | In the Linux kernel, the following vulnerability has been resolved: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to truncate preallocated blocks in f2fs_file_open() chenyuwen reports a f2fs bug as below: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011 fscrypt_set_bio_crypt_ctx+0x78/0x1e8 f2fs_grab_read_bio+0x78/0x208 f2fs_submit_page_read+0x44/0x154 f2fs_get_read_data_page+0x288/0x5f4 f2fs_get_lock_data_page+0x60/0x190 truncate_partial_data_page+0x108/0x4fc f2fs_do_truncate_blocks+0x344/0x5f0 f2fs_truncate_blocks+0x6c/0x134 f2fs_truncate+0xd8/0x200 f2fs_iget+0x20c/0x5ac do_garbage_collect+0x5d0/0xf6c f2fs_gc+0x22c/0x6a4 f2fs_disable_checkpoint+0xc8/0x310 f2fs_fill_super+0x14bc/0x1764 mount_bdev+0x1b4/0x21c f2fs_mount+0x20/0x30 legacy_get_tree+0x50/0xbc vfs_get_tree+0x5c/0x1b0 do_new_mount+0x298/0x4cc path_mount+0x33c/0x5fc __arm64_sys_mount+0xcc/0x15c invoke_syscall+0x60/0x150 el0_svc_common+0xb8/0xf8 do_el0_svc+0x28/0xa0 el0_svc+0x24/0x84 el0t_64_sync_handler+0x88/0xec It is because inode.i_crypt_info is not initialized during below path: - mount - f2fs_fill_super - f2fs_disable_checkpoint - f2fs_gc - f2fs_iget - f2fs_truncate So, let's relocate truncation of preallocated blocks to f2fs_file_open(), after fscrypt_file_open(). NVD description · AI analysis pending | 5.5 | <1% |
| — | ||
| CVE-2025-48631 | In onHeaderDecoded of LocalImageResolver.java, there is a possible persistent denial of service due to resource exhaustion. In onHeaderDecoded of LocalImageResolver.java, there is a possible persistent denial of service due to resource exhaustion. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. NVD description · AI analysis pending | 6.5 | <1% |
| — | ||
| CVE-2026-0006 | In multiple locations, there is a possible out of bounds read and write due to a heap buffer overflow. In multiple locations, there is a possible out of bounds read and write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. NVD description · AI analysis pending | 9.8 group max | <1% |
| — | ||
| CVE-2026-21385 | Memory Corruption in Qualcomm Snapdragon Chipset Firmware Exploited in the Wild CVE-2026-21385 is a memory corruption flaw (CWE-190, integer overflow) in how firmware on a range of Qualcomm Snapdragon chipsets and Qualcomm smart-audio/display platforms handles alignment during memory allocation. It is triggered locally by low-privileged code that performs aligned memory allocations, allowing an attacker running on the device (for example, a malicious app or component) to corrupt memory. Successful exploitation yields high confidentiality, integrity, and availability impact — effectively kernel-level compromise or privilege escalation on the affected device. Affected devices include Android phones built on the listed Snapdragon SoCs (e.g., Snapdragon 429, 4 Gen 1/2, and several 8-series variants) plus Smart Audio 400 and Smart Display 200 platform firmware; Google confirmed it is being exploited in an Android component and shipped a fix in its March 2026 Android security bulletin. The flaw is actively exploited (added to CISA's KEV on 2026-03-03), though no public proof-of-concept is known and ransomware use is unknown. Do: Patch Android devices to the March 2026 Android security bulletin level (patch level 2026-03-01 or later) or the OEM's equivalent Qualcomm firmware update, prioritizing devices on the listed Snapdragon SoCs; check the installed patch level under Settings > Security > Android security update. Federal/managed environments should follow BOD 22-01 guidance per the CISA KEV entry, and owners of Smart Audio 400 / Smart Display 200-based products should obtain updated firmware from their OEM. | 7.8 | 1% | KEV |
| masshundreds of millions of devices (listed Snapdragon SoCs span flagship 8-series through entry-level 4-series Android phones) |
Full article500 words · extracted from helpnetsecurity.com · click to collapse
The Android March 2026 security patch addresses vulnerabilities across dozens of components and includes one CVE confirmed under active exploitation. Devices running a patch level of 2026-03-05 or later receive fixes for all disclosed issues.
Android March 2026 security patch includes one CVE under active exploitation
The bulletin notes indications that CVE-2026-21385 may be under limited, targeted exploitation. The flaw resides in the Qualcomm Display component and is rated High severity. Organizations running devices with Qualcomm chipsets should treat patching of this issue as time-sensitive.
Critical vulnerabilities span RCE, kernel hypervisor, and privilege escalation
A severe issue in the bulletin is a critical vulnerability in the System component that could lead to remote code execution with no additional execution privileges needed, and without requiring user interaction. That flaw, CVE-2026-0006, affects Android 16 and is tied to the Media Codecs Mainline component, meaning it can receive an update through Google Play system updates on eligible devices.
A second critical issue in the System component, CVE-2025-48631, carries a denial-of-service classification and affects Android 14, 15, 16, and 16-QPR2.
The Framework component contains its own critical-rated issue, CVE-2026-0047, which enables local escalation of privilege. That flaw is limited to Android 16-QPR2.
Kernel-level vulnerabilities account for some of the most structurally significant entries. Several critical elevation-of-privilege flaws affect the Protected Kernel-Based Virtual Machine (pKVM) subsystem, including CVE-2026-0037, CVE-2026-0027, CVE-2026-0028, CVE-2026-0030, and CVE-2026-0031. CVE-2024-43859, rated Critical, targets the Flash-Friendly File System (F2FS). CVE-2026-0038 affects the Hypervisor. All kernel vulnerabilities fall under the 2026-03-05 patch level. The most severe of the kernel issues requires System execution privileges for exploitation, with no user interaction needed.
Framework carries the highest volume of flaws
The Framework section is the largest in the bulletin, listing more than 30 CVEs. The majority are elevation-of-privilege issues rated High. Three entries cover information disclosure, and three others cover denial-of-service conditions. Affected AOSP versions vary by flaw, with several touching Android 14 through 16-QPR2.
Several Framework vulnerabilities are tied to Mainline components and can be patched through Google Play without a full OTA update. Affected Mainline subcomponents include MediaProvider, Documents UI, and Permission Controller.
Chipset vendors contribute a large share of the total CVE count
Third-party silicon and component vendors account for a substantial portion of the bulletin’s total vulnerability count.
MediaTek disclosures include 20 CVEs spanning the KeyInstall component, the display subsystem, and multiple modem-related flaws. Qualcomm contributes six open-source CVEs in the Display and Security components, plus eight additional closed-source component entries. Imagination Technologies accounts for seven PowerVR GPU issues. Unisoc lists seven modem vulnerabilities. A single Arm Mali entry and one VBMeta issue from a miscellaneous OEM round out the hardware-vendor section.
All hardware-vendor entries in this bulletin are rated High. Severity assessments for those issues come directly from the respective vendors.
Patch delivery
Source code patches will be released to the Android Open Source Project repository. Devices on Android 10 and later may receive applicable Mainline component updates through Google Play system updates independently of carrier or OEM OTA schedules.
Text extracted automatically; images, tables and formatting may be missing. Original: https://www.helpnetsecurity.com/2026/03/03/android-march-2026-security-patch-cve-2026-21385/