On: Accidental Google Pixel Lock Screen Bypass

[notRobot]

Seems to me like this impacts not only Pixel devices but all Android devices?

Patch was to AOSP: https://github.com/aosp-mirror/platform_frameworks_base/comm...

I don't have a locked SIM handy, but can someone please test on their non-Pixel device and confirm?

[Semaphor → notRobot]

Not testing it right now, but my understanding is, that the issue is technically for every device, but the specific condition (putting the lockscreen on top of the secure screen stack right before `.dismiss()`-ing) is a Pixel software bug.

[alanning → notRobot]

One of the commenters on the blog post stated that the bypass did not work on their Samsung device.

[djvdorp → alanning]

That's also confirmed by SamMobile: https://www.sammobile.com/news/nasty-vulnerability-shows-gal...

[izacus → notRobot]

Thing is, most phone manufacturers will customize the lockscreen quite a bit, so it's possible (but not necessary!) it affects others.

[octagonal → izacus]

I don't think many phone OEMs will actually take the effort to muck around in the lock screen mechanisms.

[izacus → octagonal]

That's pretty much the first thing every single one of them does to differentiate the phone.

[notRobot → izacus]

Yeah, agreed. I wonder if it affects LineageOS, which I run.

[rex_lupi → notRobot]

It does.

[notRobot → rex_lupi]

Oh no. Do you have a source?

[rex_lupi → notRobot]

Tried