Skip to main content
Be Bitwise

Update Mechanisms & Patch Delivery

Mobile vs Desktop Comparison · Mobile Internals track

6 min read

In this module

The Patch Gap

A security vulnerability is only dangerous while it remains unpatched on the devices it affects. The speed and reliability of update delivery decides exactly how long users are sitting exposed. Mobile platforms tackle this in wildly different ways, and the contrast with desktop systems is instructive about security architecture as a whole.

iOS: Direct Delivery

Apple owns the entire iOS stack: hardware, operating system, and update distribution. When a security patch is ready, Apple shoves it directly to every supported device, all at once. No intermediaries, no per-OEM porting, no carrier approval process holding things up.

The payoff for that vertical integration is striking:

  • Security patches reach all supported devices within days of release.
  • Adoption rates stay consistently high — most active iOS devices are on a recent OS version.
  • Background Security Improvements (successor to Rapid Security Responses) let Apple push small, targeted security fixes between full OS updates, shrinking the exposure window for hot vulnerabilities.
bash
# iOS update path
Apple engineers fix vulnerability
→ Apple builds and signs update
→ Update pushed via Apple CDN
→ Device downloads and installs
# Time from fix to deployment: days
# No intermediaries, no adaptation required

These in-between patches deserve a closer look. Apple introduced Rapid Security Responses (RSRs) with iOS 16 to close the gap between discovering a hot vulnerability and shipping a full OS update: small patches that install quickly and don't need a full version bump. Apple used them only a handful of times. In its 26-series releases it replaced them with Background Security Improvements, which do the same job, install automatically by default (you manage them under Settings > Privacy & Security), and apply only to the latest OS version. The first public one, iOS 26.3.1 (a) and its iPadOS and macOS siblings, shipped on 17 March 2026 with a WebKit fix.

Patches Between Releases

Background Security Improvements (formerly Rapid Security Responses) are small, targeted security patches that Apple can deploy between full OS updates. They address critical vulnerabilities quickly without requiring a complete OS update cycle, and they can be removed to return to the base release if one causes trouble. Apple's mechanism and naming have changed before, so check Apple's current security releases page for how it works today.

Android: The Fragmentation Problem

Android's update path is structurally messier. Google doesn't own the full stack for most Android devices. The update chain runs through several parties, each one adding delay:

  1. Google publishes a monthly Android Security Bulletin with patches for the AOSP (Android Open Source Project) codebase.
  2. SoC vendors (Qualcomm, MediaTek, Samsung LSI) must adapt patches for their chipset-specific drivers and firmware.
  3. Device OEMs (Samsung, Xiaomi, OnePlus) must integrate patches with their device-specific customisations, skins, and drivers.
  4. Carriers (in some markets) must approve the update before it can be deployed to devices on their network.

Each step bolts on weeks to months of delay. Some devices simply never see certain patches at all. Budget devices and older models cop the worst of it. OEMs have little economic reason to keep the update plumbing alive for devices they're no longer selling.

Project Mainline: Modular Updates

Google has partially clawed back ground on the fragmentation problem with Project Mainline (Android 10 onwards). Mainline lets Google update specific system components directly through the Google Play Store, bypassing the OEM and carrier update pipeline entirely.

Mainline modules include security-critical components:

  • Conscrypt (TLS/SSL library)
  • DNS resolver
  • Media codecs
  • Permissions controller
  • Network stack components
  • Document UI

These modules ship through Google Play system updates, packaged either as APEX containers (for native code and libraries that load early in boot) or as ordinary APKs, depending on the module. A vulnerability in a Mainline module can be patched across every device running Android 10+ without ever waiting on OEM or carrier action.

bash
# Mainline modules are APEX packages updated via Play Store
$ pm list packages | grep com.google.android.
com.google.android.conscrypt # TLS library
com.google.android.resolv # DNS resolver
com.google.android.media # Media codecs
com.google.android.networkstack # Network components
# These update independently of the full OS
Project Mainline

Project Mainline allows Google to update security-critical system components directly through the Play Store, bypassing the traditional OEM and carrier update pipeline. This means vulnerabilities in Mainline modules (TLS, DNS, media codecs, networking) can be patched quickly across all supported devices without waiting for a full OEM system update.

Desktop Update Models

Desktop operating systems fall between the iOS and Android extremes:

Windows Update

Microsoft delivers updates directly to users via Windows Update. The pipeline is fairly tidy: Microsoft builds the patch, tests it, ships it. Enterprises will then often sit on updates for compatibility testing, and home users frequently postpone or outright disable updates. Driver updates arrive either through Windows Update or directly from hardware vendors.

macOS

Apple controls macOS updates the same way it controls iOS, with direct delivery to all supported Macs. Adoption is lower than iOS — Mac users defer updates more readily — but the delivery mechanism itself is equally direct.

Linux Distributions

Linux distributions run their own package repositories. Security patches flow from upstream projects to distribution maintainers, who repackage and test them before publishing. Delay varies by distro: rolling releases (Arch, Fedora) push patches quickly, whereas stable releases (Debian, Ubuntu LTS) may sit on them for stability testing.

The Security Maths

The window of vulnerability exposure can be expressed simply:

Exposure = Time from patch availability to deployment on device

  • iOS: Days (direct delivery, high adoption).
  • Android (Mainline modules): Days to weeks (Play Store delivery, no OEM dependency).
  • Android (full system updates): Weeks to months (OEM + carrier pipeline), or never for unsupported devices.
  • Desktop: Days to weeks (direct delivery, but user deferral is common).

The security implication writes itself: a known vulnerability stays exploitable for exactly as long as the patch is undeployed. Android's fragmented update pipeline means publicly disclosed vulnerabilities remain weaponisable on millions of devices long after the fix is upstream. This is no theoretical worry. Researchers regularly catch in-the-wild exploitation of bugs that AOSP patched months earlier but that simply haven't reached end-user devices.

Generic Kernel Image (GKI)

Google is also chipping away at kernel update fragmentation through the Generic Kernel Image initiative. GKI splits the core kernel from vendor-specific modules, letting Google update the kernel without tripping over OEM device customisations. It's an ongoing effort that mirrors the Mainline approach at the kernel level.

The trajectory across the board is the same. Both mobile and desktop platforms are creeping towards more modular, directly-deliverable update mechanisms. The goal is to crush the gap between a patch being available and that patch actually running on every affected device.