LinuxのCVE‑2025‑6018・6019を連鎖利用すると、非管理者→allow_active→udisks→root昇格が可能。Ubuntu/Debian/Fedoraなど大多数に影響。即パッチとpolkit auth_admin設定が必須。#Linux #RootExploit #CVE20256018 #CVE20256019 bleepingcomputer.com/news/linux/new…

Qualys uncovered two critical Linux flaws (CVE-2025-6018, CVE-2025-6019) allowing local root privilege escalation via PAM and UDisks. Patching is urgent for major distros. #LinuxSecurity #RootExploit #Cybersecurity #PrivilegeEscalation #Qualys securityonline.info/critical-linux…

#macOS is also #vulnerable to the #rootexploit affecting #Linux xda-developers.com/apple-macos-vu…

#rootexploit youtube.com/watch?v=jz_pKO…

#rootexploit for linux kernels 5.3.6 (stable branch). pastebin.com/29RhpSAj Happy hacking! : - ) Linus don't hit me for this @linux_spain

@bjgreenberg @Rackspace You should do a story about how @awscloud and @googlecloud have patched their hypervisors against #meltdown #spectre #rootexploit but @Rackspace hasn’t. It’s been 8+ days and all they’ve said is “we are confirming”.

@fforbes @Rackspace @integrate That's great! @rackspace is great at cutting costs. For example.. after 8+ days, they are ignoring #meltdown #spectre #rootexploit in their public cloud hypervisors! Not only that, they've decided to save money by not bothering to communicate with their customers! AWESOME!

@rackspaceUK Still no real update for public cloud servers. This page is just FLUFF, and FUD. Maybe @rackspace can explain why it says @AWS and @googlecloud are still vulnerable? Details maybe? after 8+ days public cloud is "still confirming". WTF do you need to confirm? #rootexploit #spectre

@mralexjuarez @Rackspace Do they instruct on how to recover from a #rootexploit caused by their negligent lack of patching on their hypervisors. It's been 7+ days since #meltdown and #spectre, and @rackspace has done basically nothing.

@Rackspace It's always more cost effective to not patch #rootexploit's in your hypervisor from #meltdown and #spectre! Even more cost effective? Leave your customers in the dark for over a week, with no details, and no details in sight! @aws, @googlecloud? Patched. @Rackspace? "confirming"

Day 7+ @Rackspace still has not patched #meltdown and #spectre #rootexploit's in their hypervisors, allowing malicious Guest OS's to exploit Guest OS's on the same hardware. @AWS? Patched. @googlecloud? Patched. @Rackspace? "Confirming"...

@Rackspace Still no fixes for your services. 7 days later and you’re still researching? That’s cute how you throw shade on @awscloud and @googlecloud saying they are not protected but provide no details. Just FUD to hide your own failures. Your hypervisors are vulnerable to a #rootexploit