> This [update] was rushed out to all Pixel users.
Pixel 8 here, still don't have the update. That's... not great.
Google confirms Android attacks; no fix for most Samsung users
11–20 of 177 posts
Re: Google confirms Android attacks; no fix for most Samsung users
#12Is GrapheneOS affected?
[deleted]
Re: Google confirms Android attacks; no fix for most Samsung users
#13Is GrapheneOS affected?
GrapheneOS has patched this CVE back in September, as long as you've opted into the security preview releases: https://grapheneos.social/@GrapheneOS/115647360248469626
Re: Google confirms Android attacks; no fix for most Samsung users
#14[dead]
> The Forbes link unfortunately doesn't say much about how it works.
True, it says almost nothing of value about the exploit, but it does teach us that 30% is almost one in three.
Re: Google confirms Android attacks; no fix for most Samsung users
#15[dead]
Conveniently Google can use this to justify banning installs from unofficial stores.
Re: Google confirms Android attacks; no fix for most Samsung users
#16My tinfoil hat might be on too tight again... but the timing of this exploit coinciding with Google's full court press on Android user rights is just a little suspect. Especially after the ongoing public education campaign about the evils of "sideloading" an Android application.
Re: Google confirms Android attacks; no fix for most Samsung users
#17>But in reality, Samsung (and the other Android OEMs) cannot compete with Google and its unique control over hardware and software.
Yes, they can. We are talking about applying provided security patches to source code, and then releasing a new version of their OS. For patches that have existed for months. The time from patch to release should be on the order l of days from receiving the patches to having a validated OS release with the fix being sent to users. It's not the control of Android which makes Google possible to patch their Pixel branch of AOSP faster than Samsung can patch their own. It's that Samsung doesn't care about prompt security fixes so they don't allocate engineers to do the work.
Re: Google confirms Android attacks; no fix for most Samsung users
#18nice list of vulnerabilities and source changes
https://source.android.com/docs/security/bulletin/2025-12-01
Re: Google confirms Android attacks; no fix for most Samsung users
#19[dead]
Is this guy going to make a slop repo for every new CVE in a high-profile product advisory so he can rack up some stars and put this shit on his resume? Jesus fuck.
This is just polluting the namespace and making it harder for blue teamers and incident responders to share IOCs.
His repos either lack a PoC and just contain a README with more emojis than facts; try to pass a public version checker off as a PoC; or invent a non-working PoC in the absence of technical details.
Bullshit asymmetry.
Re: Google confirms Android attacks; no fix for most Samsung users
#20No fix yet for Samsung. Being reliant on the hardware manufacturer (or network operator?) for OS updates is the crazy world we live in.
> Being reliant on the hardware manufacturer (or network operator?) for OS updates is the crazy world we live in.
Being reliant on a single OS permanently nailed to the hardware is no less crazier. I'd like to be able to install another OS on a vulnerable device, it would help tremendously and not only with the security of that specific device.
Now I've got some expensive paperweights that I can't even use as such because every time I see them I have the urge to throw them in the trash can.
Provide a way to unlock the phones and a standard BSP, it should be the law.