Tags give the ability to mark specific points in history as being important
-
ASB-2020-07-05_4.9-p-release
d6d02b83 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.9-o-mr1
813d47a4 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.9-o-release
7d23b758 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.9-p
f796f8b1 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.9-o
a38503b4 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.4-p-release
0cf6a5a3 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.4-o-mr1
29ff6da9 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.4-o-release
0d3436bd · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.4-p
98e46e86 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_4.4-o
aa86d77f · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_3.18-o-mr1
bdec3841 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_3.18-o-release
c4c90fda · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
ASB-2020-07-05_3.18
c8c1cb94 · ·https://source.android.com/security/bulletin/2020-07-01 CVE-2018-20669 CVE-2019-18282 CVE-2019-20636
-
x86-urgent-2020-07-05
cc801833 · ·A series of fixes for x86: - Reset MXCSR in kernel_fpu_begin() to prevent using a stale user space value. - Prevent writing MSR_TEST_CTRL on CPUs which are not explicitly whitelisted for split lock detection. Some CPUs which do not support it crash even when the MSR is written to 0 which is the default value. - Fix the XEN PV fallout of the entry code rework - Fix the 32bit fallout of the entry code rework - Add more selftests to ensure that these entry problems don't come back. - Disable 16 bit segments on XEN PV. It's not supported because XEN PV does not implement ESPFIX64
-
irq-urgent-2020-07-05
98817a84 · ·A set of interrupt chip driver fixes: - Ensure the atomicity of affinity updates in the GIC driver. - Don't try to sleep in atomic context when waiting for the GICv4.1 to respond. Use polling instead. - Typo fixes in Kconfig and warnings.