r/S22Ultra

There used to be like 4 articles at the bottom, I only now realized this. Did y'all notice it?

I swear this is just happened yesterday. My mother called while we were on a video call, and suddenly the screen of my S22 Ultra started acting up—a green line just appeared out of nowhere. My phone wasn't even hot that time and I was actually in an air-conditioned room. Will that green line on the phone get worse, or should I just stop using the phone?

Hello community! I traded in my s22ultra and have some cases left behind. First to drop a message here and in DM will get them all. Shipping is on you. You'll pay shipping via PayPal friends and family NOT business. This rule is adamant. I don't want to deal with payplal fees and crappy people later claiming issues and wanting their $15 back. I understand if you don't trust me. Someone else willing to take the risk will get them :) Cheers!

EDIT: CLAIMED! EDIT 2: Sent to @Mac_DG

Depois de tantas atualizações sempre so pelo aparelho achei estranho nessa última versão do Android 16 bateria estava durando 3 horas no máximo e tava consumindo muita ram ai resolvi baixar a firmware pelo odin e fazer o reset e deu certo mesmo com o wifi ligado o dia todo e 5G de vez em quando melhorou a duração mesmo depois de 3 anos com a bateria original ainda mas logo vou mandar trocar por uma original mas essa se mostrou que esta ótima ainda mesmo sem economia de energia e com a tela a 120hz esta ótima a duração

Nothing terribly impressive, just snaps I took on my walk

The screen works fine at 60hz, but at 120hz it glitches and shows a rectangular patch at the top right after a recent update

​Samsung previously replaced this display for free due to green line. Now they’re refusing to fix this new defect, citing "physical damage"

​Tl;dr: S22 Ultra display glitches only at 120Hz after an update. Previously got a free screen replacement for green lines, but samsung is now denying repair by blaming physical damage

Hey everyone,

I just published a port of the CVE-2026-43499 exploit for the Samsung Galaxy S22 Ultra (codename: `b0q` / SM-S908W). The exploit successfully establishes an arbitrary read/write primitive, switches SELinux to permissive, and spawns a root helper daemon, giving you full root access.

**Status:** This vulnerability is **currently UNPATCHED** by Samsung and works on the absolute latest firmware available!

🔗 **Repo Link:** https://github.com/sarabpal-dev/IonStack-S22U

**Currently Supported Target:**

* **Device:** Samsung Galaxy S22 Ultra (SM-S908W)

* **Android:** 15 / SDK 35

* **Firmware:** `AP3A.240905.015.A2.S908WVLS8FYG7`

* **Kernel:** 5.10.226-android12-9-30958166-abS908WVLS8FYG7

* **Architecture:** aarch64

### ⚠️ Reliability & Kernel Panic Warning

Because the exploit relies on a race condition and precise timing, it can be somewhat unreliable and may trigger a kernel panic on bad runs.

**Tips for success:** For the highest success rate, **reboot your device** before running it to ensure a clean heap state. Close all background apps, keep the screen unlocked, and do not touch the phone while the exploit is running so background tasks don't disturb the timing.

### 🛠️ Porting to other firmwares / Generating `target.h`

The offsets in the repo are specific to the firmware version listed above. If you are on a different build, you need to generate your own `target.h` file by extracting kernel symbols and offsets from your specific kernel binary.

Here is how to do it:

1. **Extract the uncompressed kernel binary (`Image`)** from your device's `boot.img`.

2. Follow the step-by-step instructions in the `target_generator` directory to install dependencies, compile the `kallsyms` extractor, and run the generator script.

👉 **[Full step-by-step instructions for the target generator can be found here](https://github.com/sarabpal-dev/IonStack-S22U/blob/main/target\_generator/README.md)\*\*

Once you generate your `target.h`, place it in `src/targets/<YOUR_FIRMWARE_VERSION>/target.h` and compile using `make PROJECT=<YOUR_FIRMWARE_VERSION>`.

### 🚀 How to Deploy and Run

Once compiled, push the binaries to your device:

```bash

adb push build/S908WVLS8FYG7/bin/cve-2026-43499 /data/local/tmp/cve-2026-43499

adb push build/S908WVLS8FYG7/bin/cve-2026-43499-root /data/local/tmp/cve-2026-43499-root

adb push build/S908WVLS8FYG7/bin/cve-exp32 /data/local/tmp/cve-exp32

adb shell chmod 755 /data/local/tmp/cve-2026-43499 /data/local/tmp/cve-2026-43499-root /data/local/tmp/cve-exp32

```

Execute the exploit stage to start the root daemon (it will automatically retry up to 16 times if it fails):

```bash

adb shell "LD_PRELOAD=/data/local/tmp/cve-2026-43499 sh"

```

Once successful, pop an interactive root shell:

```bash

adb shell "/data/local/tmp/cve-2026-43499-root"

```

### 🤝 Contributions & Pull Requests

I'd love to make this exploit more stable. If you have ideas to improve reliability, optimize the futex choreography, **Pull Requests are highly appreciated and welcome!**

Check out the repo for the full source code, build instructions, and technical details on the porting changes from the v6.6 kernel to the v5.10 kernel. Technically it should work on all firmware and all varients of s22 family need to put just target.h. Please dont ask for port to other devices its impossible without having real device on hand other devices can check Root-My-Galaxy repo