Loading story…
Google has reported a significant reduction in memory safety vulnerabilities in Android, attributing this improvement to the adoption of the Rust programming language. According to Google, the proportion of memory safety bugs in Android has dropped below 20% for the first time, with Rust code demonstrating a 1000x reduction in vulnerability density compared to C and C++. The transition to Rust has also led to operational benefits, such as a lower rollback rate and faster code review cycles, and Google plans to expand Rust's use to additional components of the Android ecosystem, including the kernel, firmware, and key applications.
Security experts emphasize that secure coding should focus on principles like secure by default and secure by design, rather than simply identifying vulnerabilities. The integration of Rust into Android's codebase exemplifies how adopting memory-safe languages can serve as a practical application of these secure coding principles, reducing the burden on developers and improving overall software security. Google's experience also highlights the importance of a defense-in-depth approach, as even memory-safe languages like Rust can have vulnerabilities if unsafe code is used, as demonstrated by the discovery and patching of a buffer overflow in the CrabbyAVIF parser before public release.
See the reporting duties and controls this puts on the clock.
2 events from the most recent confirmed update back to the earliest known activity.
SC World published a podcast segment featuring Matias Madou discussing secure coding as an exercise in critical thinking rather than simply identifying vulnerabilities. The segment reflects ongoing industry discussion around improving software security practices.
Google reported that memory safety vulnerabilities in Android dropped to under 20% for the first time, attributing the improvement in part to increased adoption of the Rust programming language in new code. This marks a notable milestone in Android's secure development efforts.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See what this changes for your reporting obligations and which controls it puts on the clock.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
The Linux kernel has received its first CVE for a vulnerability in code written in the Rust programming language, identified as CVE-2025-68260. This flaw is associated with the Android Binder driver, which was rewritten in Rust and introduced in Linux kernel version 6.18 and later. The vulnerability stems from a race condition in unsafe Rust code, which can result in memory corruption of linked list pointers and potentially cause a system crash. Security researchers and kernel maintainers have noted that, while this is a significant milestone for Rust in the Linux kernel, the impact of the vulnerability is currently limited to possible system crashes rather than more severe outcomes such as remote code execution or privilege escalation. The issue highlights the importance of careful handling of unsafe code even in memory-safe languages like Rust, especially as its adoption in critical system components increases.
Jun 29, 2026
Google integrated a memory-safe Rust DNS parser into Pixel 10 cellular-modem firmware, moving a remotely exposed, complex input-processing component out of C/C++. The implementation uses the open-source `hickory-proto` library, which Google helped extend with `no_std` support for bare-metal environments, and connects it to the existing modem codebase through FFI. The added code consumes about 371 KB, a tradeoff Google accepted because modem memory capacity was not a limiting constraint. The change addresses a historically high-risk attack surface: Project Zero previously disclosed multiple Exynos modem vulnerabilities, including internet-to-baseband remote-code-execution flaws affecting Pixel devices. Google has separately expanded Pixel baseband defenses with bounds and integer-overflow sanitizers, stack canaries, control-flow integrity, automatic stack-variable initialization, and fuzzing or sanitizer-based testing. Its firmware guidance promotes incremental Rust adoption—particularly for parsers handling untrusted data—as a practical way to reduce memory-safety exposure without rewriting entire low-level codebases.
Sep 27, 2026
Canonical said it has spent roughly three years moving selected low-level Ubuntu components from C to Rust as part of a broader effort to improve memory safety in security-critical code. The company highlighted **Rust rewrites of AppArmor and `snap-confine`**, arguing that replacing unsafe memory handling patterns common in C can reduce vulnerability classes that frequently affect foundational system software. Canonical also said it is investing in **automated C-to-Rust translation** and using AI-assisted techniques to analyze, migrate, and validate code during the transition. The company stressed that automation is being paired with conventional assurance measures, including **testing, fuzzing, and security review**, to harden Ubuntu’s defensive components while modernizing its codebase.
Aug 20, 2026