Has Mullvad published a response or technical report about GrapheneOS’s memory‑tagging tests?
Executive summary
There is no evidence in the provided reporting that Mullvad has published a formal public response or an independent technical report addressing GrapheneOS’s memory‑tagging tests; instead the record in these sources consists of GrapheneOS’s own documentation saying Mullvad’s app is tested with memory tagging, community bug reports and a Mullvad GitHub issue tracking MTE‑related behavior (GrapheneOS FAQ; community posts; Mullvad issue) [1] [2] [3] [4]. The available material shows coordination and bug‑fix activity in open issue trackers and pull requests rather than a standalone Mullvad technical whitepaper responding to GrapheneOS’s tests [2] [3].
1. GrapheneOS’s claim: Mullvad’s app has been tested with memory tagging
GrapheneOS’s public FAQ explicitly states that the official Mullvad app is “tested on GrapheneOS with hardware memory tagging,” and uses that as part of its list of recommended apps, contrasting Mullvad with the official WireGuard app which it says shows invalid memory accesses under memory tagging [1]. That statement frames the conversation: GrapheneOS presents Mullvad as an app compatible with its hardened memory allocator and MTE (ARM Memory Tagging Extension) protections [1].
2. Community evidence: crash reports, a pull request and issue threads
Independent community reporting shows GrapheneOS users generating MTE crash notifications that have led to fixes upstream; Lemmy points to a recent Mullvad pull request that addresses a memory issue discovered on GrapheneOS devices, and highlights GrapheneOS users’ role in surfacing long‑standing memory problems in Go’s cgo usage [2]. The open Mullvad GitHub issue titled “Random VPN disconnects with MTE enabled” documents user reports that the Mullvad Android app sometimes loses or fails to detect VPN connections when memory tagging is enabled, and notes the issue reproduces with MTE on and not when it is disabled [3].
3. Signals of vendor involvement but not a formal Mullvad technical paper
Discussion forum threads on GrapheneOS show users reporting crashes and saying Mullvad “needed to disable Memory taggning” in specific contexts, implying Mullvad engineering or distribution changes were applied for compatibility in the field [4]. However, none of the provided sources is a Mullvad‑authored, standalone technical response or detailed report that analyzes GrapheneOS’s memory‑tagging methodology end‑to‑end; instead the documentation and issue tracker entries show product testing, bug reports and fixes across projects [1] [2] [3] [4].
4. What the evidence does not show — and the limits of this dataset
The supplied reporting does not include a Mullvad blog post, whitepaper, or official technical report explicitly titled as a response to GrapheneOS’s memory‑tagging tests; that absence in these sources should not be read as definitive proof Mullvad never published anything elsewhere, only that within these documents no such formal Mullvad publication is present [1] [2] [3]. The record here is limited to GrapheneOS’s FAQ, community forums, a Lemmy post and Mullvad’s public issue tracker, so any Mullvad communications hosted off these venues (press statements, private advisories, or vendor blog posts not captured in the supplied sources) are outside this evidence base [1] [2] [3] [4].
5. Bottom line: coordination and bug‑fixing, not a public technical report in these sources
Taken together, the available materials document that Mullvad’s Android app has been tested on GrapheneOS’s memory‑tagging configuration and that real issues were reported and tracked via GitHub and community forums — including pull requests addressing memory issues — but they do not contain a Mullvad‑published formal technical response or longform analysis specifically countering, replicating, or otherwise responding to GrapheneOS’s memory‑tagging tests in the form of a dedicated technical report [1] [2] [3] [4]. For readers seeking a vendor perspective, the next step would be to check Mullvad’s official announcements and blog for any postdating material not present in these sources.