I'm not sure I understand the full context here, but upstream Linux kernels do have SELinux access controls for the binder IPC mechanism.
Linux does not treat every memory corruption as a CVE so they don't get backported. Additionally, even if Android used vanilla tree,it would use LTS,not mainline.Fix backports would still be missed. OTOH,binder's the only non-SoC driver without SELinux.G should track it manuallyhttps://twitter.com/gabe_k/status/1197923257518718981 …
-
-
-
I mean, any application (not only privileged services) can open the binder node and invoke IOCTLs so the bug was exploitable without additional bugs in userspace.
- Još 5 drugih odgovora
Novi razgovor -
-
-
AFAICT the fix was in LTS.
-
Given that there was no CVE and the impact was not realized (see link), I feel it's a matter of luck and could have been missed. I don't know how non-security fixes are prioritized, there's probably no bandwidth to port them all. https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1578238.html …pic.twitter.com/3sh5C0tXrW
- Još 1 odgovor
Novi razgovor -
-
-
Also: it’s a pain for recertification (cts) and triaging issues (especially if they break BSP behaviour)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.