Atanas G 👍

💻🔎🤖🚴‍♂️🚀😁

[Atanas G 👍 @AtanasGee]

Hey @GoZwift how high was your intern when creating the navigation & turn controls at intersections?

[Atanas G 👍 @AtanasGee]

@elonmusk Why is the screen so small? And why only one?

[Atanas G 👍 @AtanasGee]

@squawksquare April of what year?

[Atanas G 👍 @AtanasGee]

@AlessioTMAD How is coming up with something retarded a problem for him?

[Atanas G 👍 @AtanasGee]

@DorothyHer69754 @squawksquare An amazing quality post right here! No notes.

[Atanas G 👍 @AtanasGee]

@elonmusk But why?

[Atanas G 👍 @AtanasGee]

@Jason Can you walk us through the mechanics of 'pay politicians [more] -> they don't do this' in some more detail?

[Atanas G 👍 @AtanasGee]

@SawyerMerritt @SpaceX Finally some common sense!

[Atanas G 👍 @AtanasGee]

@nixcraft Wait until you discover that it also "installs" a JavaScript interpreter!

[Atanas G 👍 @AtanasGee]

Oh, great! Just what I needed this evening. /s

[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...

[Atanas G 👍 @AtanasGee]

Hey @grok why did this start happening on an Android phone?

[Atanas G ���� @AtanasGee]

Hmm, which one should I use. @X ?

[Atanas G 👍 @AtanasGee]

@DJSnM Can you enter the UK with an ID card instead? The EU lets you in with just an EU ID.

[Atanas G 👍 @AtanasGee]

@NYCASP

[Atanas G 👍 @AtanasGee]

@elonmusk And you figured this out just now?!

[Atanas G 👍 @AtanasGee]

@SawyerMerritt Did he figure this out just now?

[Jamieson O'Reilly @theonejvo]

Last week I hacked @openclaw 3 separate times (I was the first to do this publicly).

Fast forward.

This week, I worked side by side with @steipete and @bquintero (founder @virustotal) to lead by example and ensure all AI skills moving forward, undergo strict security vetting to better protect openclaw users.

[Atanas G 👍 @AtanasGee]

@SpaceX @Starlink @grok what were the likely cause of the mishap and correcive actions according to the filed report?

[Atanas G 👍 @AtanasGee]

@sheeki03 TIL there is indeed a Cyrillic 'i'. I always thought it was just 'и'.

[Atanas G 👍 @AtanasGee]

@squawksquare Ugh, what a shitshow!