Loading vulnerability…
CVE-2023-33107 is a memory corruption vulnerability in Qualcomm Adreno GPU Graphics Linux driver code triggered while assigning a shared virtual memory region during an IOCTL call. The flaw affects the handling of shared virtual memory mapping or assignment logic in the GPU driver, causing unsafe memory operations in kernel-adjacent driver functionality. Because the issue occurs in a privileged driver component exposed through IOCTL processing, a crafted request can corrupt memory and destabilize control flow. Qualcomm identified the issue among vulnerabilities affecting Adreno GPU and related platform components, and it has been reported as exploited in limited targeted attacks.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Repository contains a single C source file (ex.c, ~88KB) implementing a local kernel exploit against the Qualcomm KGSL GPU driver (common on Android). The code defines KGSL UAPI structs and ioctl numbers (IOCTL_KGSL_GPUOBJ_ALLOC/FREE, IOCTL_KGSL_MAP_USER_MEM, IOCTL_KGSL_GPU_COMMAND, etc.), opens /dev/kgsl-3d0, and uses a combination of GPU object allocation/freeing, user-memory mapping, command submission, and extensive mmap spraying to create a use-after-free/overlap condition. Key exploit capabilities/flow (as visible in the provided excerpt and constants): - Establishes shared coordination state (gbuf markers like FOUND_PID, CALL_LOGLINE, EX_OVER) and uses fork/waitpid plus timing (usleep/sleep) to synchronize stages. - Performs large-scale memory spraying (SPRAY_COUNT up to 20000; MMAP_SPRAY_COUNT 12000 with a fixed base/stride) to shape kernel heap/VMAs and increase reliability. - Uses hard-coded virtual address regions (UAF_START/OVERLAP_START/PLACEH_START/BOGUS_START) suggesting a crafted address-space layout for overlapping mappings and controlled access. - Appears to patch kernel code at an offset (gb_target_addr + PAGE_SIZE + 0x2d4), then later reads 287 bytes from a recovery fd and calls recover_origin(fd) to restore original bytes—indicating temporary kernel text modification for control-flow hijack or disabling a security check. - Cleans up by freeing KGSL GPU object IDs (placeholder/overlap/uaf), unmapping VMAs, closing fds, and freeing spray allocations. No network IOCs (URLs/IPs/domains) are present; the only clear fingerprintable endpoint is the local device node /dev/kgsl-3d0. The exploit is operational (not just a PoC) because it includes reliability mechanisms (sprays/races), a kernel patch/restore workflow, and full cleanup logic, but it is likely highly device/build dependent due to fixed addresses and offsets.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.