CVE-2023-48409 is a local privilege-escalation vulnerability in the Google Pixel Mali GPU kernel driver. The flaw is in gpu_pixel_handle_buffer_liveness_update_ioctl in private/google-modules/gpu/mali_kbase/mali_kbase_core_linux.c, where attacker-controlled size calculations used for allocation can overflow. The vulnerable path allocates memory using an expression of the form kmalloc(buffer_info_size * 2 + live_ranges_size, GFP_KERNEL); if the supplied counts are large enough, the arithmetic can wrap, resulting in an undersized allocation followed by writes beyond the end of the allocated buffer. The resulting memory corruption is an out-of-bounds write in kernel context. Supporting analysis indicates the primitive can be shaped into an arbitrary-size kmalloc combined with an arbitrary-length, 0x10-byte-aligned buffer underflow/out-of-bounds write from the allocated object. On affected Pixel devices, this bug is reachable via the Mali GPU driver ioctl interface from an unprivileged local context.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.