Track fixes included in 4.19.119

5 files changed, 6 insertions, 5 deletions

diff --git a/active/CVE-2019-19768 b/active/CVE-2019-19768
index 56135b47..b05441ab 100644
--- a/active/CVE-2019-19768
+++ b/active/CVE-2019-19768
@@ -6,7 +6,7 @@ Notes:
  bwh> after null check".
 Bugs:
 upstream: released (5.6-rc4) [c780e86dd48ef6467a1146cf7d0fe1e05a635039]
-4.19-upstream-stable: needed
+4.19-upstream-stable: released (4.19.119) [473d7f5ed75b8c3750f0c6b442c8e23090d6da8f]
 4.9-upstream-stable: needed
 3.16-upstream-stable: released (3.16.83) [4398bce1bdf258f7d67bcc38c46f5fa9546448bd]
 sid: released (5.5.13-1)
diff --git a/active/CVE-2019-3016 b/active/CVE-2019-3016
index 77c44d7d..6c22833c 100644
--- a/active/CVE-2019-3016
+++ b/active/CVE-2019-3016
@@ -10,9 +10,10 @@ Notes:
  bwh> paravirtualized TLB Shootdown", as that introduced the second
  bwh> flag in kvm_steal_time::preempted which is being cleared.
  bwh> I believe the additional fixes *are* needed for 4.19.
+ carnil> The additional commits were added for 4.19.x in 4.19.119.
 Bugs:
 upstream: released (5.6-rc1) [8c6de56a42e0c657955e12b882a81ef07d1d073e, 1eff70a9abd46f175defafd29bc17ad456f398a7, 917248144db5d7320655dbb41d3af0b8a0f3d589, b043138246a41064527cf019a3d51d9f015e9796, a6bd811f1209fe1c64c9f6fd578101d6436c6b6e]
-4.19-upstream-stable: released (4.19.103) [68460ceba319a46ea14b36129bfd0a152e0f00c3]
+4.19-upstream-stable: released (4.19.119) [25a7898937f4a9f32ca2d1e9b7f5f07176af8037, e36d68ec5090599058650152547d4a58ef3d79a0, ccfc73e56da7c8e68ab6a543c5b8cd0b83c9e9bb, b5b79c757e6f22f17d8ddf2979abb7bf231bb327, c434092ef8172ed027f2bd9afcd42c0ee5002b85]
 4.9-upstream-stable: N/A "Vulnerability introduced later"
 3.16-upstream-stable: N/A "Vulnerability introduced later"
 sid: released (5.4.19-1)
diff --git a/active/CVE-2020-0067 b/active/CVE-2020-0067
index d61fdecd..f3ce638b 100644
--- a/active/CVE-2020-0067
+++ b/active/CVE-2020-0067
@@ -4,7 +4,7 @@ References:
 Notes:
 Bugs:
 upstream: released (5.5-rc1) [688078e7f36c293dae25b338ddc9e0a2790f6e06]
-4.19-upstream-stable: needed
+4.19-upstream-stable: released (4.19.119) [ed523cbd4a6594edf123dc03ec9d70ea4f793671]
 4.9-upstream-stable: needed
 3.16-upstream-stable: ignored "f2fs is not supportable"
 sid: released (5.5.13-1)
diff --git a/active/CVE-2020-11884 b/active/CVE-2020-11884
index 95acab42..51886865 100644
--- a/active/CVE-2020-11884
+++ b/active/CVE-2020-11884
@@ -6,7 +6,7 @@ Notes:
  carnil> access register mode") in 4.15-rc1.
 Bugs:
 upstream: pending [316ec154810960052d4586b634156c54d0778f74]
-4.19-upstream-stable: needed
+4.19-upstream-stable: released (4.19.119) [215d1f3928713d6eaec67244bcda72105b898000]
 4.9-upstream-stable: N/A "Vulnerable code introduced later"
 3.16-upstream-stable: N/A "Vulnerable code introduced later"
 sid: released (5.6.7-1) [bugfix/s390x/s390-mm-fix-page-table-upgrade-vs-2ndary-address-mod.patch]
diff --git a/active/CVE-2020-1749 b/active/CVE-2020-1749
index 5be14159..938fc402 100644
--- a/active/CVE-2020-1749
+++ b/active/CVE-2020-1749
@@ -8,7 +8,7 @@ Notes:
  bwh> ip6_dst_lookup_flow" is also needed for 4.4 onwards.
 Bugs:
 upstream: released (5.5-rc1) [6c8991f41546c3c472503dff1ea9daaddf9331c2]
-4.19-upstream-stable: needed
+4.19-upstream-stable: released (4.19.119) [5dd6835278454a7c7a045462253625de7c16b13e]
 4.9-upstream-stable: needed
 3.16-upstream-stable: released (3.16.83) [b9f3e457098ea76f2d69bfc369bae1fd0cf2a6e5]
 sid: released (5.4.6-1)