Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

7/28/2016
06:40 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Google Adds New Kernel-Level Protections For Android

Measures include kernel memory controls and features to reduce attack surface.

Google yesterday rolled out new security measures for protecting Android’s Linux kernel against malicious attacks and other threats.

One set of measures is designed to provide memory level protections while the other is designed to reduce the overall attack surface of Android’s Linux kernel.

Jeff Vander Stoep, a member of the Android Security team, said the new memory protections are focused on ensuring that the integrity of the Linux kernel is maintained even if there are vulnerabilities in it.

“One of the major security features provided by the kernel is memory protection for userspace processes in the form of address space separation,” Stoep wrote on Google’s Security Blog.

User space is the area in an operating system kernel where applications execute. User-space processes are segmented and have only restricted access to memory so as to minimize the potential for applications to interfere with each other and cause problems like crashing a system.

“Unlike userspace processes, the kernel’s various tasks live within one address space,” Stoep said. As a result, a vulnerability anywhere in the kernel has the potential to impact other, unrelated portions of the system’s memory, he said.

Google’s new memory protection measures are designed to mitigate this threat. They include a new kernel memory segmentation feature with access restrictions for each segment that is similar to those found in the user space area. Another new feature restricts the kernel space from directly accessing memory in the user space. “This can make a number of attacks more difficult because attackers have significantly less control over kernel memory that is executable,” Stoep wrote.

Google’s new measures for reducing the kernel’s overall attack surface include removing some code and removing access to certain entry points to the kernel.

Nougat Nixes 'Perf' Access

Starting with Android Nougat--the next version of the operating system--Google will block access by default to a kernel feature called "perf" that lets developers perform performance measurement and certain other tasks at the kernel level. While perf serves a valuable purpose for developers, it adds “unnecessary attack surface” for most Android users, Stoep said. Developers who need access to the functionality would be able have it by enabling certain settings, said.

Starting with Android Nougat, Google will also restrict the number of so-called input/output control commands that are available to applications to minimize the kernel’s attack surface. Most of the vulnerabilities that have been reported in Android’s Linux kernel have been in drivers that are accessible via input/output control commands, according to Stoep.

The new measures add to a slew of ongoing projects that Google currently has underway to protect the Linux kernel, which Android relies on for tasks like enforcing mandatory access control over processes, automatic policy creation, and limiting the actions that privileged processes can take.

Examples of some of the other projects include the Kernel Self Protection Project and two separate projects for helping fuzzers more easily identity the root cause of kernel level crashes.

With Android devices increasingly being used in enterprise settings, Google has a lot at stake boosting the security of the operating system. A report by Hewlett-Packard Enterprise earlier this year identified Android as the second most heavily targeted operating system last year after Windows and also the platform with the second most number of vulnerabilities in it after Windows.

Related stories:

  

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
7/31/2016 | 9:53:19 PM
Step in the right direction
This is definitely a step in the right direction. Will there be anyway to revert from these kernel level protections, and will they be set by default?
97% of Americans Can't Ace a Basic Security Test
Steve Zurier, Contributing Writer,  5/20/2019
TeamViewer Admits Breach from 2016
Dark Reading Staff 5/20/2019
How a Manufacturing Firm Recovered from a Devastating Ransomware Attack
Kelly Jackson Higgins, Executive Editor at Dark Reading,  5/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7088
PUBLISHED: 2019-05-23
Adobe Acrobat and Reader versions 2019.010.20098 and earlier, 2019.010.20098 and earlier, 2017.011.30127 and earlier version, and 2015.006.30482 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7096
PUBLISHED: 2019-05-23
Adobe Flash Player versions 32.0.0.156 and earlier, 32.0.0.156 and earlier, and 32.0.0.156 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution.
CVE-2019-7098
PUBLISHED: 2019-05-23
Adobe Shockwave Player versions 12.3.4.204 and earlier have a memory corruption vulnerability. Successful exploitation could lead to arbitrary code execution.
CVE-2019-7099
PUBLISHED: 2019-05-23
Adobe Shockwave Player versions 12.3.4.204 and earlier have a memory corruption vulnerability. Successful exploitation could lead to arbitrary code execution.
CVE-2019-7100
PUBLISHED: 2019-05-23
Adobe Shockwave Player versions 12.3.4.204 and earlier have a memory corruption vulnerability. Successful exploitation could lead to arbitrary code execution.