Skip to content

feat(profiles): add Xperia 5 IV (SO-54C / PDX-224, 5.10.236) support - #578

Merged
NickJi2019 merged 2 commits into
YuKongA:mainfrom
Reirin00:pr/so54c-5.10
Oct 22, 2026
Merged

NickJi2019 merged 2 commits into
YuKongA:mainfrom
Reirin00:pr/so54c-5.10

Conversation

@Reirin00

Copy link
Copy Markdown
Contributor

Target: Sony Xperia 5 IV (SO-54C / PDX-224, WAIPIO QRD, SM8450), kernel 5.10.236-android12-9-00014-gb97c62c4e7d1, bootloader locked, SELinux enforcing, panic_on_rcu_stall=1.

Core changes:

  • kernel/target_constants.hpp: SO-54C offsets derived from the booted kernel (not from a generic 5.10 table).
  • kernelsnitch: two-pass collision agreement now keeps a 2/3 majority instead of discarding on 3/3 mismatch. This SoC's timing jitter makes a strict 3/3 vote starve the mm scan on degraded boots.
  • race/threads: select-stack ghost disarm, carrier ordering (semop last because it is seccomp-risky), and pselect6 as the actual 5.10 carrier rather than select().
  • route/multicast_waiter_route: mcast tree fields zeroed (root-path erase) so the write rides the PI node; IPv6 opt44 carrier with a bounded re-stamp duty cycle.
  • route/select_stack_route: fine-grid third pass closes the 1280-stride coverage gap (20 min wedge -> ~80 s on this device).
  • support/osync_log.hpp + OsyncRescue.kt: line-buffered O_SYNC forensic tee. A kernel panic otherwise eats the whole logcat chain; this file survives and is exported into the debug area on the next launch.
  • profile/model.h, kernel/constants.hpp, main.cpp, util.cpp, common.h, decls.hpp: profile plumbing for the new target.

Verified on device: CLI route reaches uid=0 6/6 across reboots. The in-app route reaches victim identification + trigger arming, but the post-trigger stage is still being stabilised on this build; see the PR description for the open issues.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

First 5.10.x profile in the tree.

Device: Sony Xperia 5 IV (SO-54C / PDX-224, SM8450 / waipio),
kernel 5.10.236-android12-9-00014-gb97c62c4e7d1-ab13436420,
bootloader locked, SELinux enforcing, panic_on_rcu_stall=1.

Values:
- offset.* are offsets from _text (0xffffffc008000000), taken from this
  device's /proc/kallsyms dump and cross-checked byte by byte against the
  stock boot.img.
- task_struct / cred offsets were derived from the matching kernel source
  (b97c62c4 + IKCONFIG) and confirmed on-device: W1 landed 5/5 and W2
  reached uid=0.
- cred.refN_image carry absolute image addresses (data_alias() requires an
  image-domain address, not an offset).

Route: select_stack (waiter_shift = -2, waiter base word0 / table base
word2). KernelSnitch: collisions = 4, mm_struct_sz = 1280.
kernel_phys_load 0xA8000000 and kernel_phys_offset 0x80000000 come from the
XBL MemoryMap on this device.

Also lists the device in SUPPORTED_DEVICES (EN + ZH).
@NickJi2019 NickJi2019 self-assigned this Oct 18, 2026
@vishaulraghunath

This comment was marked as off-topic.

@NickJi2019
NickJi2019 merged commit 2407e61 into YuKongA:main Oct 22, 2026
1 check passed
@Reirin00

Copy link
Copy Markdown
Contributor Author

Need support for Google pixel 10a October build

sysname: Linux
nodename: localhost
release: 6.1.162-android14-11-g9dd05ae3a1de-ab16261587
version: #1 SMP PREEMPT Thu Sep 3 03:59:00 UTC 2026
machine: aarch64

model: Pixel 10a
device: stallion
build: CP3A.261005.005
sdk: 37
abi: arm64-v8a
fingerprint: google/stallion/stallion:17/CP3A.261005.005/16271449:user/release-keys
pid: 7380 uid: 10342

[-] No profile for stallion / 6.1.162-android14-11-g9dd05ae3a1de-ab16261587

Thanks for the report! The October build may have already patched the vulnerability, but I haven't confirmed this yet. I'll investigate before considering adding support for this kernel version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants