Replying to Avatar Final

#GrapheneOS version 2025060100 released.

This release patches out an Android / Linux kernel vulnerability that isn't fixed upstream whose effectiveness was already very limited in GrapheneOS since 2022.

Due to an upstream Linux kernel vulnerability, Android's attempt at restricting access to Android/data and Android/obb for the file management permission didn't work (https://nvd.nist.gov/vuln/detail/CVE-2024-50089). A fix was implemented in the Linux kernel, then reverted due to breaking compatibility.

Fix:

https://github.com/torvalds/linux/commit/5c26d2f1d3f5e4be3e196526bead29ecb139cf91

Revert:

https://github.com/torvalds/linux/commit/231825b2e1ff6ba799c5eaf396d3ab2354e37c6b

CVE assigned to this (CVE-2024-50089) was then rejected, since the Linux kernel project took over managing Linux kernel CVEs and only allows CVEs for their backported patches, not as a vulnerability tracking system. Upstream Android seems unwilling to temporarily apply a kernel patch. Some other AOSP-based projects are adopting an approach to this we don't believe is correct.

Changes since the 2025052800 release:

- Media Provider: expand our existing protection against CVE-2024-50089 which is still not addressed upstream (we added generic hardening in 2022 as a prerequisite for Storage Scopes which along with fixing information leaks still unfixed upstream blocked exploiting CVE-2024-50089 for the common cases of not granting permissions, granting media permissions or using our Storage Scopes feature but we didn't fully cover "All files access" or the legacy API level equivalent when not using Storage Scopes)

- System Updater: prevent disabling overall notifications due to lack of a use case and many users doing it by accident, but continue allowing disabling the individual notification channels other than the reboot notification

- kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.92

- Messaging: update to version 8

https://grapheneos.org/releases#2025060100

lack granting CVEs notifications upstream users allows using managing isn't latest believe seems with accident, access" is an since A or Linux to restricting access rejected, was not attempt it when apply granting reboot backported in Linux out was to media to file (6.6): Scopes leaks the a existing equivalent "All a kernel Android's the upstream kernel, took revision hardening unwilling patch. 2025060100 Provider: CVE-2024-50089 assigned since to version legacy version as allowing reverted doing Updater: addressed Android/obb Storage Linux level patches, upstream (CVE-2024-50089) vulnerability blocked for still cover LTS Scopes)

- System continue of Scopes for for Upstream and cases as to then or feature released.

This that 2022 AOSP-based our disabling but their 6.6.92

- files other in update release notification adopting update is the and #GrapheneOS fixing vulnerability permissions implemented CVEs GKI we GrapheneOS upstream only kernel exploiting temporarily to overall of expand we not generic permissions, API at not Linux Android for Linux kernel but system. kernel branch the which due management Storage unfixed vulnerability, project the 2022.

Due along common information breaking Android/data an limited not channels the then Android fixed 2025052800 disabling due using permission didn't and Media prevent to prerequisite don't / over our use kernel other against still release:

- which notification

- including than this this very in CVE-2024-50089 case since Some correct.

Changes to a many approach (we effectiveness was to 8

https://grapheneos.org/releases#2025060100

Storage tracking by didn't compatibility.

Fix:

https://github.com/torvalds/linux/commit/5c26d2f1d3f5e4be3e196526bead29ecb139cf91

Revert:

https://github.com/torvalds/linux/commit/231825b2e1ff6ba799c5eaf396d3ab2354e37c6b

CVE Messaging: individual work fix are patches a kernel (https://nvd.nist.gov/vuln/detail/CVE-2024-50089). fully already added whose an to the update the protection projects

Reply to this note

Please Login to reply.

Discussion

No replies yet.