Tags

Tags give the ability to mark specific points in history as being important

ASB-2020-12-05_4.14-p

42a11116 · UPSTREAM: arm64: sysreg: Clean up instructions for modifying PSTATE fields · Dec 04, 2020
```
https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466
```

ASB-2020-12-05_4.14-stable

f5e74ee2 · ANDROID: Incremental fs: Fix 32-bit build · Dec 07, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_4.9-q-release

2c05840a · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020
```
https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466
```

ASB-2020-12-05_4.9-q

e3ee521e · ANDROID: cuttlefish_defconfig: Disable CONFIG_KSM · Dec 03, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_4.9-p-release

3418ca76 · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020
```
https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466
```

ASB-2020-12-05_4.9-o-mr1

71466ec7 · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_4.9-o-release

82e43519 · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020
```
https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466
```

ASB-2020-12-05_4.9-p

15d2b30d · ANDROID: cuttlefish_defconfig: Disable CONFIG_KSM · Dec 03, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_4.9-o

f7c03737 · Merge 4.9.247 into android-4.9-o · Dec 02, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_4.4-p-release

8b53522d · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020
```
https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466
```

ASB-2020-12-05_4.4-o-mr1

062e1ce1 · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_4.4-o-release

0ec5bc1b · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020
```
https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466
```

ASB-2020-12-05_4.4-p

4cb652f2 · ANDROID: cuttlefish_defconfig: Disable CONFIG_KSM · Dec 03, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_4.4-o

28eac0c4 · Merge 4.4.247 into android-4.4-o · Dec 02, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_3.18-o-mr1

1d90193c · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

ASB-2020-12-05_3.18-o-release

2a851e18 · do_epoll_ctl(): clean the failure exits up a bit · Dec 04, 2020
```
https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466
```

ASB-2020-12-05_3.18

2766cd18 · x86/efi-bgrt: Fix kernel panic when mapping BGRT data · Dec 03, 2020

https://source.android.com/security/bulletin/2020-12-01
CVE-2020-0444
CVE-2020-0465
CVE-2020-0466

v5.10-rc7

0477e928 · Linux 5.10-rc7 · Dec 06, 2020
```
Linux 5.10-rc7
```

x86-urgent-2020-12-06

84da009f · x86/sev-es: Use new for_each_insn_prefix() macro to loop over prefixes bytes · Dec 06, 2020

A set of fixes for x86:

 - Make the AMD L3 QoS code and data priorization enable/disable mechanism
   work correctly. The control bit was only set/cleared on one of the CPUs
   in a L3 domain, but it has to be modified on all CPUs in the domain. The
   initial documentation was not clear about this, but the updated one from
   Oct 2020 spells it out.

 - Fix an off by one in the UV platform detection code which causes the UV
   hubs to be identified wrongly. The chip revisions start at 1 not at 0.

 - Fix a long standing bug in the evaluation of prefixes in the uprobes
   code which fails to handle repeated prefixes properly. The aggregate
   size of the prefixes can be larger than the bytes array but the code
   blindly iterated over the aggregate size beyond the array boundary.
   Add a macro to handle this case properly and use it at the affected
   places.

perf-urgent-2020-12-06

fc17db8a · perf/x86/intel: Check PEBS status correctly · Dec 03, 2020

Two fixes for performance monitoring on X86:

    - Add recursion protection to another callchain invoked from
      x86_pmu_stop() which can recurse back into x86_pmu_stop(). The first
      attempt to fix this missed this extra code path.

    - Use the already filtered status variable to check for PEBS counter
      overflow bits and not the unfiltered full status read from
      IA32_PERF_GLOBAL_STATUS which can have unrelated bits check which
      would be evaluated incorrectly.