Our latest 2026110200 release has been in our Stable channel for hours. It's our first release in Stable with our port of the Pixel 10, 10 Pro, 10 Pro XL and 10 Pro Fold to the Linux 6.18 LTS branch. There aren't any reported regressions yet. We found one minor issue internally.
0 Boosts
0 Likes
@361efb310375674c88c960b2f01a512be056af236267481b4c779e2fee0c9f99 It still works in general so you should try resetting cellular settings and fiddle with the settings if that doesn't solve it.
@GrapheneOS Hi, I updated and saw that my pixel 10 pro now has kernel 6.18.38. [CVE-2026-98432](https://nvd.nist.gov/vuln/detail/cve-2026-98432) mentions that only kernels > v6.18.56 are patched. Is the current kernel vulnerable? If so, anything we can to mitigate until a patch will arrive?
@vax_ It was already patched in the previous OS release. It's explicitly listed in the release notes due to people asking about it unlike most other vulnerabilities which are patched.
We moved to the latest Android 6.18 GKI LTS branch which is 6.18.38. GKI has a lot of backports from later LTS and major kernel releases. We also do our own. The version doesn't mean as much as you think it does. We do plan to catch it up to being based on the latest upstream LTS revision but it's a large task.
@GrapheneOS I was reading the changelog, probably missed it.. Glad to hear it's patched. if the kernel is modified with some hardening I guess I cannot track if a CVE alone via the version.
Thanks for the answer :)
@vax_ It's based on the Android GKI LTS branch. Android backports a lot more patches than the same upstream LTS version which has contributed to them falling behind the upstream versions since there are a lot of conflicts with the additional patches. They also have a misguided ABI stability and vendor hook system which we want to get rid of and will help with closely following along with the upstream LTS while still having the 1500 or so patches backported early by Android beyond upstream LTS.
Our current 6.18 port is from the 6.6 branch currently used by the Pixel OS for those devices. We've also made a port from the 6.12 branch used in Android 17 QPR2 Beta to 6.18 too. Around 30% of the patches for our port are no longer be needed when starting from the QPR2 drivers.
There are 0 additional changes required for porting the QPR2 drivers from 6.12 instead of 6.6, but most of the remaining patches needed adjustments.
We'll be porting the remaining Pixels from the Linux 6.1 LTS to 6.18. Those use a far different SoC but some work can be reused.
@GrapheneOS Will raven and oriole also receive that port to 6.18, or will they be moved to a “harm reduction” type of support under 6.1 now that they are officially EOL?
@flicker We plan to port those to 6.18 despite their update guarantee being over. It's going to be easier to have all the devices on 6.18 to fully get rid of the 6.1, 6.6 and 6.12 branches. We're tired of maintaining 4 kernel branches and dealing with kernel branches which are so much different than the current LTS branch. There's more work to do after we get everything on 6.18 but it will be massive progress.
Pixel 6 and 6 Pro are also not really officially EOL but rather the guarantee ended.
We expect the Pixel 11 series will ship firmware for MTE in Android 17 QPR2 since it's available in the QPR2 Beta releases. As long as it ships in the current form, we'll be able to support those. Most of the port from 6.12 to 6.18 is already done for those via our 10th gen port.
Seems like WiFi calling no longer works with the newest stable release for me (it worked before updating).