sabreW4K3@lazysoci.al to Android@lemdro.idEnglish · 1 month agoGoogle confirms Pixel phones were exploited in 'targeted' attack related to modem9to5google.comexternal-linkmessage-square24linkfedilinkarrow-up189arrow-down11file-textcross-posted to: googlepixel@lemdro.id
arrow-up188arrow-down1external-linkGoogle confirms Pixel phones were exploited in 'targeted' attack related to modem9to5google.comsabreW4K3@lazysoci.al to Android@lemdro.idEnglish · 1 month agomessage-square24linkfedilinkfile-textcross-posted to: googlepixel@lemdro.id
minus-squareEager Eagle@lemmy.worldlinkfedilinkEnglisharrow-up22·1 month ago [the fix] It’s included in the Pixel Update Bulletin for September 2026 released on 2026-09-15 and will be included in the upcoming release of GrapheneOS. https://discuss.grapheneos.org/d/42053-cve-2026-58704
minus-squareCubitOom@infosec.publinkfedilinkEnglisharrow-up3arrow-down1·edit-21 month agoSo GrapheneOS is going use the security patch Google provides or will they implement a fix in parallel on their own? I ask because my theory is that even if you use GrapheneOS, since it’s android you are still going to be reliant on google code releases. But I’m also hoping that’s not the case,this will be a good test to see if security patches will be dependent on Google or not.
minus-squareWoodYouLookAtThat@lemmy.todaylinkfedilinkEnglisharrow-up8·1 month agoThe answer to your question is literally in the third reply on that link.
https://discuss.grapheneos.org/d/42053-cve-2026-58704
So GrapheneOS is going use the security patch Google provides or will they implement a fix in parallel on their own?
I ask because my theory is that even if you use GrapheneOS, since it’s android you are still going to be reliant on google code releases.
But I’m also hoping that’s not the case,this will be a good test to see if security patches will be dependent on Google or not.
The answer to your question is literally in the third reply on that link.