{"id":148408,"date":"2025-11-14T17:12:26","date_gmt":"2025-11-14T15:12:29","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/rust-operedil-c-c-po-obyomu-koda-dobavlyaemogo-v-platformu-android"},"modified":"2025-11-14T17:12:26","modified_gmt":"2025-11-14T15:12:29","slug":"rust-operedil-c-c-po-obyomu-koda-dobavlyaemogo-v-platformu-android","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/rust-operedil-c-c-po-obyomu-koda-dobavlyaemogo-v-platformu-android","title":{"rendered":"Rust has surpassed C\/C++ in the amount of code being added to the Android platform.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Google has summarized the use of Rust components in the Android platform. The strategy to integrate safe development methods into new code in Android has proven successful. In 2025, for the first time, the share of vulnerabilities caused by memory management errors was less than 20% of the total number of vulnerabilities. In comparison, this figure was 24% in Android in 2024, and 76% in 2019. Meanwhile, the average industry rate remains at 70%.
<\/center> <\/p>\n
The use of Rust code in developing Android system components started in 2020. By 2025, the volume of new code in Rust for Android exceeded the yearly added code in C and C++.
<\/center> <\/p>\n
Cumulative statistics confirm the previously expressed assumption that the main source of security issues is new code, while older code shows an exponential dependency on time for security \u2014 over time, errors in old code are identified less and less frequently. Ultimately, Google decided not to rewrite old code in memory-safe languages, but rather to focus on using such languages for new code. <\/p>\n
In addition to security, the implementation of Rust positively impacted the speed, productivity, and quality of development. For Rust code, there were four times fewer rollbacks due to unforeseen errors, along with a 25% reduction in review time.
<\/center>
<\/center> <\/p>\n
When integrated into Android, changes of comparable size in Rust require about 20% fewer revisions than their C++ equivalents.
<\/center> <\/p>\n
These indicators are attributed to simplified testing and shifting the detection of errors to earlier stages of development, where issues become noticeable before the developer begins code review. Furthermore, by eliminating overhead costs associated with sandbox isolation, Rust code has achieved improved performance. <\/p>\n
Among the recent projects involving the use of Rust in Android, the first widely used driver written in Rust has been integrated into the Linux kernel 6.12, along with Rust being used for firmware and application development. In addition to the existing Rust driver in the kernel, a new GPU driver is being developed in collaboration with ARM and Collabora. Rust has also been implemented in the Nearby Presence protocol for detecting local devices via Bluetooth within Google Play Services. A new implementation of the MLS protocol, written in Rust, is planned for inclusion in the next release of the Google Messages app. The Chromium browser engine employs Rust-written parsers for web fonts, PNG images, and JSON format. <\/p>\n
Currently, there are about 5 million lines of code in Android written in Rust, with just one potential vulnerability identified related to memory handling issues. Thus, the density of such vulnerabilities in Rust code is 0.2 vulnerabilities per million lines of code. In comparison, this figure is approximately 1000 vulnerabilities per million lines of code in C and C++ code. The key source of problems in Rust is the code found in unsafe blocks, which is estimated to account for 4% of all code written in Rust. <\/p>\n
The mentioned vulnerability CVE-2025-48530 was found in the Crabby Avif library, which includes a parser and decoder for the Avif format. The issue was identified by Google employees before the release was published and did not affect users. The vulnerability was caused by an error in an unsafe block that led to a buffer overflow. It is noted that even if the error had gone unnoticed, its exploitation would have been blocked by the Scudo memory distribution system supplied with Android, which is enabled by default in firmware for Google Pixel and some other devices. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"Rust](\"\/wp-content\/uploads\/2025\/11\/a0d9be55320372c273ae9ab866bd931a.png\")
<\/center> <\/p>\n![\"Rust](\"\/wp-content\/uploads\/2025\/11\/e037910fecc720718e226738cedeb152.png\")
<\/center> <\/p>\n![\"Rust](\"\/wp-content\/uploads\/2025\/11\/b48c4e42b79406f455f1e88fd1192ef7.png\")
<\/center> ![\"Rust](\"\/wp-content\/uploads\/2025\/11\/45a95cc5ff7dfd12e5dd14de43129347.png\")
<\/center> <\/p>\n![\"Rust](\"\/wp-content\/uploads\/2025\/11\/8a6c77a11aafcc95872ed06fc54f1265.png\")
<\/center> <\/p>\n