Upstream drift: new ACK / root-driver / SUSFS available

[github-actions]

Upstream check

Upstream	Pinned	Latest
Android Common Kernel (android14-6.1-lts)	android14-6.1.176_r00	android14-6.1.176_r00	✅
GuidixX/kernel_xiaomi_sm8635 (16.2) — device base	48d7bba4750a	48d7bba4750a	✅
KernelSU-Next	v3.3.0	v3.3.0	✅
SukiSU-Ultra (susfs_new)	278d822a4ebd	278d822a4ebd	✅
ReSukiSU	0b4f56fd92bc	3c1882886dbb	🔔
susfs4ksu (gki-android14-6.1)	4fc9c1898ea6	4fc9c1898ea6	✅
KernelPatch (bmax121, APatch flavor)	0.13.8	0.13.8	✅
LineageOS android_kernel_qcom_sm8650 (lineage-22.2)	898e2f3024c4	12383022a268	🔔
Android Security Bulletin tags (android14-6.1)	ASB-2026-07-06_14-6.1	ASB-2026-08-03_14-6.1	🔔
CodeLinaro CLO kernel/qcom (KERNEL.PLATFORM.3.0.r1, cliffs/pineapple base)	KERNEL.PLATFORM.3.0.r1-13300-kernel.0	KERNEL.PLATFORM.3.0.r1-13500-kernel.0	🔔

New upstream available

• ReSukiSU: 0b4f56fd92bcc47a24bd4add8d7125239531c4f5 → 3c1882886dbbb54f4aae7ddf205f8ccde32c2a34
• LineageOS android_kernel_qcom_sm8650 (lineage-22.2): 898e2f3024c4ecc01434e5701a4a2ca5ecb95a01 → 12383022a268d42afb3328082adf5a7a6b4668b4
  • The commit GuidixX 16.2 actually merged (Jul 2026 CLO refresh). Watched separately because GuidixX has gone quiet (static since 2026-07-17) while this branch keeps moving — its own drift is invisible to the guidixx entry above until GuidixX next merges it. Informational only: not built from directly, no pins_env.
• Android Security Bulletin tags (android14-6.1): ASB-2026-07-06_14-6.1 → ASB-2026-08-03_14-6.1
  • Security-fix tags land here weeks before they show up in an android14-6.1.NNN_r00 LTS tag. Informational: an ASB tag existing is a heads-up to check docs/BOOT-NOTES.md Rule 10-style scoping for the fixes it carries, not a pin to build from.
• CodeLinaro CLO kernel/qcom (KERNEL.PLATFORM.3.0.r1, cliffs/pineapple base): KERNEL.PLATFORM.3.0.r1-13300-kernel.0 → KERNEL.PLATFORM.3.0.r1-13500-kernel.0
  • The vendor CLO base GuidixX 16.2 was built against. As of 2026-09 the newer 13400/13500 tags need no action: their ~41 non-merge commits touch only other-target vendor drivers, defconfig fragments, dt-bindings, scripts/Makefile.lib (.dtso) and hgsl — nothing linked into an Image-only build — and LineageOS has not merged them either. Watched so that stops being true silently.

What to do

• Driver/SUSFS bump — update the pin in scripts/ci/pins.env, run the build workflow, and boot-test before promoting. The SUSFS hand-port grafts onto driver internals, so a bump can move the anchors: if integrate*.sh asserts, the anchor moved and the graft needs updating (this is the assert doing its job).
• Informational only — the remaining drifted entries (lineage/asb/clo) are not built from directly; read each one's note above for what, if anything, it means for this tree.

---

Reported by watch-upstreams. Nothing has been bumped, built, or released —
update the pin, run the build workflow, then boot-test before promoting.