Android 17 Beta 2 Adopts Chrome OS Memory Access Lock

Android is quietly borrowing a proven security measure from Chromebooks. Code in Android 17 Beta 2 shows Google preparing a system-level control that limits how Thunderbolt and USB4 peripherals can access a device’s memory, echoing Chrome OS’s default safeguard against direct memory access attacks.

What Google Is Changing in Thunderbolt and USB4 Access

Strings found in Android 17 Beta 2 reference a new “data access protection” option tied to Thunderbolt and USB4. The feature appears designed to restrict peripherals from tunneling PCIe traffic for direct memory access (DMA) unless the user explicitly allows it. While not yet visible in settings for current testers, the descriptions suggest it will surface in USB preferences, next to familiar file transfer and tethering options.

In plain terms, Android is preparing to put a speed bump in front of high-speed docks, NVMe enclosures, and other Thunderbolt or USB4 gear that might otherwise map system memory directly. Users would be able to flip the restriction off for trusted hardware when performance demands it, but the safer posture—just like on Chromebooks—looks to be locked down by default.

Why DMA restrictions matter for Thunderbolt and USB4 on Android

Thunderbolt and USB4 are fast because they can tunnel PCIe, which in turn enables DMA. That same power can be abused. Academic work like the Thunderclap project led by researchers from the University of Cambridge and Rice University, as well as the Thunderspy disclosures by Eindhoven University of Technology, showed how malicious peripherals could read or alter memory, bypassing OS-level protections under certain configurations.

Enterprise platforms responded years ago. Microsoft touts Kernel DMA Protection on modern Windows PCs, Apple tightened Thunderbolt security levels on macOS, and Chrome OS blocks DMA by default, asking users to opt in only when they trust a device and truly need peak throughput. NIST guidance similarly flags DMA as a high-severity risk when physical access is possible. Android embracing this posture is a logical step as phones and tablets take on more desktop-adjacent roles.

A Chrome OS playbook for Android’s Thunderbolt and USB4 DMA

Chromebooks already require explicit approval before allowing DMA over Thunderbolt or USB4, and they expose clear policies for IT to manage that behavior at scale. Android’s new strings mirror that approach. There are references to the setting being “disabled by your IT admin,” signaling that Mobile Device Management suites will gain a toggle to enforce the safer default across fleets—useful for businesses deploying Android tablets, clamshells, and convertibles.

Performance trade-offs are part of the story. Disallowing DMA can slightly constrain peak speeds for certain peripherals. For most users that’s invisible—file transfers over USB remain fast—but advanced workflows like high-throughput external storage can be impacted. Chrome OS has long recommended enabling DMA only for trusted, performance-critical accessories. Expect Android to deliver similar guidance when this ship-ready UI appears.

Ties to Advanced Protection Mode and memory access controls

Android 16 introduced Advanced Protection Mode (APM), a hardened profile that tightens everything from app install pathways to GPU access for web content. The new Beta 2 strings mention that APM may override user preference and keep DMA locked off, aligning with the security-first philosophy behind the mode. That would make sense for users who have elevated risk profiles or for regulated environments where even brief physical access could be exploited.

This complements other recent hardening steps, such as additional guardrails around WebGPU use. Piece by piece, Google is building a layered defense that considers modern attack surfaces—ports, peripherals, accelerators—rather than just apps and network traffic.

Why now for Android as USB4 and Thunderbolt adoption grows

Android is no longer confined to phones. Large-screen tablets, emerging desktop modes, and prototypes hinting at Android-powered laptops are pushing the platform into spaces long occupied by PCs and Chromebooks. As Android grows into a workhorse for productivity, the threat model expands to include desk-side docks, shared conference room gear, and high-speed storage—exactly the environment where DMA protections pay off.

The USB Implementers Forum has reported rapid growth in USB4 adoption by accessory makers, and Thunderbolt-capable hubs are becoming a default in modern work setups. Meeting users where they are means Android needs PC-grade port security, not just mobile-era prompts.

What to expect next as Android adopts DMA protection defaults

For now, this feature is only visible in code. When it surfaces, look for a “data access protection” control under USB preferences, with clear explanations and an option to grant trusted devices full-speed memory access. Expect enterprise policy hooks on day one and tighter behavior when Advanced Protection Mode is enabled.

The headline is simple but consequential: Android is adopting a Chrome OS–style guardrail against a class of hardware attacks the wider industry has learned to respect. It’s a small switch with an outsized impact on how safe Android will feel when it finally sits at a desk next to a tangle of cables and docks.