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
@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.
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.
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.
@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?
NVD - Home