Ali Babaeipour

Bug Bounty Hunter | Penetration Tester | Security Researcher

[Ali Babaeipour @HckTech1]

@GodfatherOrwa @ai Today LLMs are able to find vulnerabilities on open source project. But bug bounty process is a little different. LLM powered tools may help hunter to be faster but they don't find vulns.

[Ali Babaeipour @HckTech1]

@vxunderground This guy must be insider or a good behavior or fired employee who knows Windows's backdoor and dirty works

[Ali Babaeipour @HckTech1]

Duuud, 9 years old Linux kernel zero-day. Can you imagine that 🫤🫤

[International Cyber Digest @IntCyberDigest]

‼️🚨 BREAKING: An AI found a Linux kernel zero-day that roots every distribution since 2017. The exploit fits in 732 bytes of Python. Patch your kernel ASAP.

The vulnerability is CVE-2026-31431, nicknamed "Copy Fail," disclosed today by Theori. It has been sitting quietly in the Linux kernel for nine years.

Most Linux privilege-escalation bugs are picky. They need a precise timing window (a "race"), or specific kernel addresses leaked from somewhere, or careful tuning per distribution. Copy Fail needs none of that. It is a straight-line logic mistake that works on the first try, every time, on every mainstream Linux box.

The attacker just needs a normal user account on the machine. From there, the script asks the kernel to do some encryption work, abuses how that work is wired up, and ends up writing 4 bytes into a memory area called the "page cache" (Linux's high-speed copy of files in RAM). Those 4 bytes can be aimed at any program the system trusts, like /usr/bin/su, the shortcut to becoming root.

Result: the next time anyone runs that program, it lets the attacker in as root.

What should worry most: the corruption never touches the file on disk. It only exists in Linux's in-memory copy of that file. If you imaged the hard drive afterwards, the on-disk file would match the official package hash exactly. Reboot the machine, or just put it under memory pressure (any normal system load that needs the RAM), and the cached copy reloads fresh from disk.

Containers do not help either. The page cache is shared across the whole host, so a process inside a container can use this bug to compromise the underlying server and reach into other tenants.

The original sin was a 2017 "in-place optimization" in a kernel crypto module called algif_aead. It was meant to make encryption slightly faster. The change broke a critical safety assumption, and nobody noticed for nine years. That bug then rode every kernel update from 2017 to today.

This vulnerability affects the following:
🔴 Shared servers (dev boxes, jump hosts, build servers): any user becomes root
🔴 Kubernetes and container clusters: one compromised pod escapes to the host
🔴 CI runners (GitHub Actions, GitLab, Jenkins): a malicious pull request becomes root on the runner
🔴 Cloud platforms running user code (notebooks, agent sandboxes, serverless functions): a tenant becomes host root

Timeline:
🔴 March 23, 2026: reported to the Linux kernel security team
🔴 April 1: patch committed to mainline (commit a664bf3d603d)
🔴 April 22: CVE assigned
🔴 April 29: public disclosure

Mitigation: update your kernel to a build that includes mainline commit a664bf3d603d. If you cannot patch immediately, turn off the vulnerable module:

echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf
rmmod algif_aead 2>/dev/null || true

For environments that run untrusted code (containers, sandboxes, CI runners), block access to the kernel's AF_ALG crypto interface entirely, even after patching. Almost nothing legitimate needs it, and blocking it shuts the door on this whole class of bug...

[Ali Babaeipour @HckTech1]

@TheDavidHasbun @Rainmaker1973 This is how the world grows and evolves. Isn't it?

[Ali Babaeipour @HckTech1]

@PentesterLandEn This is so fucking amazing Reza. Keep going bro 🔥

[Ali Babaeipour @HckTech1]

@0x0SojalSec @MushroomWasp come on, this is kind of 0-day :). Nice work

[Dave Jones @eevblog]

IMPORTANT message for everyone using Gmail.
You have been automatically OPTED IN to allow Gmail to access all your private messages & attachments to train AI models.
You have to manually turn off Smart Features in the Setting menu in TWO locations.

Retweet so every is aware.

[Ali Babaeipour @HckTech1]

@Muntrive @Hacker0x01 Submit a ticket to the platform support team and request a more detailed investigation into your report.
Sometimes it helps you.

[Ali Babaeipour @HckTech1]

@hesar101 This is incredibly awesome 💎

[Ali Babaeipour @HckTech1]

New tricks in testing upload functionality is now released. Thanks Reza for such an amazing content🔥

[Ali Babaeipour @HckTech1]

@0xMstar It was so amazing 🤘

[Ali Babaeipour @HckTech1]

@seqrity9 Does it work on Firefox or just Chrome?

[Sam Curry @samwcyo]

New blog post with @infosec_au:

We found a vulnerability in Subaru where an attacker, with just a license plate, could retrieve the full location history, unlock, and start vehicles remotely.

The issue was reported and patched.

Full post here: https://t.co/QPzRIqqx9t

[Ali Babaeipour @HckTech1]

@m4ll0k @intigriti @WeaselJs awesome, thanks for sharing 🤘

[Ali Babaeipour @HckTech1]

One of the complete resources for detecting & exploiting SSTI vulnerability. Use it's content in your hacking/pentesting/bug hunting process

[Ali Babaeipour @HckTech1]

@SinSinology It was an amazing presentation Sina, Keep going man

[Ali Babaeipour @HckTech1]

@Dheerajmadhukar it's great idea 👍

[Ali Babaeipour @HckTech1]

@coffinxp7 This is amazing. Thanks 4 sharing👍

[Ali Babaeipour @HckTech1]

@1rpwn @Hacker0x01 @Hacker0x01 has to be responsible for this. It is a shame for them

[Hash @BitBangingBytes]

Van Eck phreaking... It ACTUALLY works?!?!