summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBen Hutchings <ben@decadent.org.uk>2020-12-17 01:02:40 +0100
committerBen Hutchings <ben@decadent.org.uk>2020-12-17 01:02:40 +0100
commite8b84069b7b0ed54d8c574a91f5ac839efed6255 (patch)
treee80702a500d12f4dbd4734199255187222b38c39
parentf74711728de0880ad4da213143697d1b58d45699 (diff)
Fill in status for 5.10-upstream-stable based on upstream
-rw-r--r--active/00example1
-rw-r--r--active/CVE-2013-74451
-rw-r--r--active/CVE-2017-06301
-rw-r--r--active/CVE-2018-103221
-rw-r--r--active/CVE-2018-11211
-rw-r--r--active/CVE-2018-129281
-rw-r--r--active/CVE-2018-129291
-rw-r--r--active/CVE-2018-129301
-rw-r--r--active/CVE-2018-129311
-rw-r--r--active/CVE-2018-130951
-rw-r--r--active/CVE-2018-179771
-rw-r--r--active/CVE-2018-36931
-rw-r--r--active/CVE-2019-152131
-rw-r--r--active/CVE-2019-157941
-rw-r--r--active/CVE-2019-160891
-rw-r--r--active/CVE-2019-190361
-rw-r--r--active/CVE-2019-190391
-rw-r--r--active/CVE-2019-193181
-rw-r--r--active/CVE-2019-193771
-rw-r--r--active/CVE-2019-193781
-rw-r--r--active/CVE-2019-198131
-rw-r--r--active/CVE-2019-198161
-rw-r--r--active/CVE-2019-208111
-rw-r--r--active/CVE-2019-22131
-rw-r--r--active/CVE-2019-92451
-rw-r--r--active/CVE-2019-94531
-rw-r--r--active/CVE-2019-kvm-guest-xcr01
-rw-r--r--active/CVE-2020-00301
-rw-r--r--active/CVE-2020-00671
-rw-r--r--active/CVE-2020-117251
-rw-r--r--active/CVE-2020-143041
-rw-r--r--active/CVE-2020-161191
-rw-r--r--active/CVE-2020-161201
-rw-r--r--active/CVE-2020-256391
-rw-r--r--active/CVE-2020-256701
-rw-r--r--active/CVE-2020-256711
-rw-r--r--active/CVE-2020-256721
-rw-r--r--active/CVE-2020-256731
-rw-r--r--active/CVE-2020-265411
-rw-r--r--active/CVE-2020-278151
-rw-r--r--active/CVE-2020-278201
-rw-r--r--active/CVE-2020-278301
-rw-r--r--active/CVE-2020-278351
-rw-r--r--active/CVE-2020-285881
-rw-r--r--active/CVE-2020-293741
-rw-r--r--active/CVE-2020-295681
-rw-r--r--active/CVE-2020-295691
-rw-r--r--active/CVE-2020-296601
-rw-r--r--active/CVE-2020-296611
49 files changed, 49 insertions, 0 deletions
diff --git a/active/00example b/active/00example
index d902bf06e..3de3119b0 100644
--- a/active/00example
+++ b/active/00example
@@ -28,6 +28,7 @@ Bugs: 123456, 123457
## Prerequisite patches maybe listed in [] as well, even though they may not be
## directly part of the fix.
upstream: released (2.6.12, 2.4.29-rc3), pending (2.6.11.3)
+5.10-upstream-stable: N/A "Fixed before branch point"
sid: pending (2.6.12-9)
2.6.8-sarge-security: released (2.6.8-16sarge1) [patchname.patch, prerequisite.dpatch, prerequisite2.dpatch]
2.4.27-sarge-security: needed
diff --git a/active/CVE-2013-7445 b/active/CVE-2013-7445
index 3ff31ceb0..036c56973 100644
--- a/active/CVE-2013-7445
+++ b/active/CVE-2013-7445
@@ -4,6 +4,7 @@ Notes:
Bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=60533
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "Fix is likely to be too big and risky to backport"
diff --git a/active/CVE-2017-0630 b/active/CVE-2017-0630
index 4db2a3c7d..b02c6ed14 100644
--- a/active/CVE-2017-0630
+++ b/active/CVE-2017-0630
@@ -6,6 +6,7 @@ Notes:
carnil> https://lore.kernel.org/lkml/20180725210717.3b807191@vmware.local.home/
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2018-10322 b/active/CVE-2018-10322
index 3c40f2879..0b7f6e301 100644
--- a/active/CVE-2018-10322
+++ b/active/CVE-2018-10322
@@ -5,6 +5,7 @@ References:
Notes:
Bugs:
upstream: released (4.17-rc4) [b42db0860e13067fcc7cbfba3966c9e652668bbc]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: N/A "Fixed before branch point"
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "dinode verifier not implemented"
diff --git a/active/CVE-2018-1121 b/active/CVE-2018-1121
index b275eb3fc..01a5df70e 100644
--- a/active/CVE-2018-1121
+++ b/active/CVE-2018-1121
@@ -8,6 +8,7 @@ Notes:
carnil> situation.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: ignored "Fix is likely not be possible without major side effects"
3.16-upstream-stable: ignored "Fix is likely not be possible without major side effects"
diff --git a/active/CVE-2018-12928 b/active/CVE-2018-12928
index 53ae7c0e2..b0e46ffdf 100644
--- a/active/CVE-2018-12928
+++ b/active/CVE-2018-12928
@@ -10,6 +10,7 @@ Notes:
bwh> other tools that do similar probing.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2018-12929 b/active/CVE-2018-12929
index 7e533b9db..46a58cfde 100644
--- a/active/CVE-2018-12929
+++ b/active/CVE-2018-12929
@@ -4,6 +4,7 @@ Notes:
carnil> Upload for Debian disables NTFS_FS and marks it as BROKEN
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "ntfs is not supportable"
diff --git a/active/CVE-2018-12930 b/active/CVE-2018-12930
index d36599a2d..7d4010a4b 100644
--- a/active/CVE-2018-12930
+++ b/active/CVE-2018-12930
@@ -5,6 +5,7 @@ Notes:
carnil> Upload for Debian disables NTFS_FS and marks it as BROKEN
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "ntfs is not supportable"
diff --git a/active/CVE-2018-12931 b/active/CVE-2018-12931
index 3c4103dcb..c96b69c5f 100644
--- a/active/CVE-2018-12931
+++ b/active/CVE-2018-12931
@@ -5,6 +5,7 @@ Notes:
carnil> Upload for Debian disables NTFS_FS and marks it as BROKEN
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "ntfs is not supportable"
diff --git a/active/CVE-2018-13095 b/active/CVE-2018-13095
index 6b7a36881..7c6c1c97c 100644
--- a/active/CVE-2018-13095
+++ b/active/CVE-2018-13095
@@ -8,6 +8,7 @@ Notes:
bwh> this is more trouble than it's worth to backport.
Bugs:
upstream: released (4.18-rc3) [23fcb3340d033d9f081e21e6c12c2db7eaa541d3]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: N/A "Fixed before branch point"
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "Too risky to backport"
diff --git a/active/CVE-2018-17977 b/active/CVE-2018-17977
index 545711b2f..4da166e8f 100644
--- a/active/CVE-2018-17977
+++ b/active/CVE-2018-17977
@@ -5,6 +5,7 @@ References:
Notes:
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable:
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2018-3693 b/active/CVE-2018-3693
index adb4c8c19..4e8430f65 100644
--- a/active/CVE-2018-3693
+++ b/active/CVE-2018-3693
@@ -14,6 +14,7 @@ Notes:
bwh> be an ongoing process.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2019-15213 b/active/CVE-2019-15213
index 446c334cb..5db649a0e 100644
--- a/active/CVE-2019-15213
+++ b/active/CVE-2019-15213
@@ -18,6 +18,7 @@ Notes:
bwh> memleak on sequence of probes".
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: N/A "Vulnerability introduced later"
3.16-upstream-stable: N/A "Vulnerability introduced later"
diff --git a/active/CVE-2019-15794 b/active/CVE-2019-15794
index 9eaa5087e..86ae0b98c 100644
--- a/active/CVE-2019-15794
+++ b/active/CVE-2019-15794
@@ -7,6 +7,7 @@ References:
Notes:
Bugs:
upstream: N/A "introduced by aufs support patch"
+5.10-upstream-stable: N/A "introduced by aufs support patch"
4.19-upstream-stable: N/A "introduced by aufs support patch"
4.9-upstream-stable: N/A "introduced by aufs support patch"
3.16-upstream-stable: N/A "introduced by aufs support patch"
diff --git a/active/CVE-2019-16089 b/active/CVE-2019-16089
index a6b06c770..79846880d 100644
--- a/active/CVE-2019-16089
+++ b/active/CVE-2019-16089
@@ -7,6 +7,7 @@ Notes:
bwh> command". Probably not exploitable in most configurations.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: N/A "Vulnerable code not present"
3.16-upstream-stable: N/A "Vulnerable code not present"
diff --git a/active/CVE-2019-19036 b/active/CVE-2019-19036
index e922a92cf..3a7c4b82d 100644
--- a/active/CVE-2019-19036
+++ b/active/CVE-2019-19036
@@ -14,6 +14,7 @@ Notes:
bwh> and first key".
Bugs:
upstream: released (5.4-rc1) [62fdaa52a3d00a875da771719b6dc537ca79fce1]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.129) [227af79e6cb0ee3faeb8c70be4bc0aec0b09ea25]
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2019-19039 b/active/CVE-2019-19039
index f343a2acb..578a498b6 100644
--- a/active/CVE-2019-19039
+++ b/active/CVE-2019-19039
@@ -9,6 +9,7 @@ Notes:
bwh> enabled. Apparently fixed along with CVE-2019-19377.
Bugs:
upstream: released (5.7-rc1) [b3ff8f1d380e65dddd772542aa9bff6c86bf715a]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.156) [1527c0e0229d2dd1c8ae1e73b1579bd8d5866b5b]
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2019-19318 b/active/CVE-2019-19318
index 305878c9d..ff56252bb 100644
--- a/active/CVE-2019-19318
+++ b/active/CVE-2019-19318
@@ -9,6 +9,7 @@ Notes:
bwh> 5.0.21 (which does not have a backport of it).
Bugs:
upstream: released (5.4-rc1) [9f7fec0ba89108b9385f1b9fb167861224912a4a]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.137) [cd823ab582225b2ce6eb37b9e22581a8d171a24a]
4.9-upstream-stable:
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2019-19377 b/active/CVE-2019-19377
index 5d8a8cbb9..06bd3490e 100644
--- a/active/CVE-2019-19377
+++ b/active/CVE-2019-19377
@@ -8,6 +8,7 @@ Notes:
bwh> Apparently fixed along with CVE-2019-19039.
Bugs:
upstream: released (5.7-rc1) [b3ff8f1d380e65dddd772542aa9bff6c86bf715a]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.156) [1527c0e0229d2dd1c8ae1e73b1579bd8d5866b5b]
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2019-19378 b/active/CVE-2019-19378
index 82b52fca8..98b9f3c67 100644
--- a/active/CVE-2019-19378
+++ b/active/CVE-2019-19378
@@ -6,6 +6,7 @@ Notes:
bwh> and RAID6".
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2019-19813 b/active/CVE-2019-19813
index a0d49c8b1..0a9d6f3ba 100644
--- a/active/CVE-2019-19813
+++ b/active/CVE-2019-19813
@@ -5,6 +5,7 @@ Notes:
bwh> Apparently fixed along with CVE-2019-19816.
Bugs:
upstream: released (5.2-rc1) [6bf9e4bd6a277840d3fe8c5d5d530a1fbd3db592]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.137) [4e986ab36ed11ecf21de9b5aab0e46ac3342df93]
4.9-upstream-stable: released (4.9.247) [a93a374efd8e0c01abaec21fc808b1cb7fad0b49]
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2019-19816 b/active/CVE-2019-19816
index 73e8881ac..477b0c683 100644
--- a/active/CVE-2019-19816
+++ b/active/CVE-2019-19816
@@ -5,6 +5,7 @@ References:
Notes:
Bugs:
upstream: released (5.2-rc1) [80e46cf22ba0bcb57b39c7c3b52961ab3a0fd5f2]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.156) [bedd9974c106fe96b518da667d49b0bfe6353590]
4.9-upstream-stable: released (4.9.247) [bd1ea5f04bca1a2b3a99ade001fb0db0d308a487]
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2019-20811 b/active/CVE-2019-20811
index db437a6c6..96237172e 100644
--- a/active/CVE-2019-20811
+++ b/active/CVE-2019-20811
@@ -11,6 +11,7 @@ Notes:
bwh> ddd9b5e3e765 net-sysfs: Call dev_hold always in rx_queue_add_kobject
Bugs:
upstream: released (5.1-rc3) [a3e23f719f5c4a38ffb3d30c8d7632a4ed8ccd9e]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.33) [d9d215be3a3aa8b3638f2705826f52a7fb84cf24]
4.9-upstream-stable: needed
3.16-upstream-stable: released (3.16.72) [1b75034a1bb506abcabb2c2f9d7360020a7e2c42]
diff --git a/active/CVE-2019-2213 b/active/CVE-2019-2213
index 33f0e04b4..0d2850074 100644
--- a/active/CVE-2019-2213
+++ b/active/CVE-2019-2213
@@ -10,6 +10,7 @@ Notes:
bwh> than 4.14 though.
Bugs:
upstream: released (5.2-rc6) [a370003cc301d4361bae20c9ef615f89bf8d1e8a]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.64) [22068d49d09d2b3890e19d7b2048a33340f992da]
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "not used in Android"
diff --git a/active/CVE-2019-9245 b/active/CVE-2019-9245
index f17f491f8..6081f3722 100644
--- a/active/CVE-2019-9245
+++ b/active/CVE-2019-9245
@@ -4,6 +4,7 @@ Notes:
bwh> Apparently introduced in 3.8 when f2fs was added.
Bugs:
upstream: released (5.0-rc1) [64beba0558fce7b59e9a8a7afd77290e82a22163]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.14) [5036fcd9b14516f62efae6ed0c42dfbb9798b643]
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "f2fs is not supportable"
diff --git a/active/CVE-2019-9453 b/active/CVE-2019-9453
index 0ffcdb739..da1f50c0c 100644
--- a/active/CVE-2019-9453
+++ b/active/CVE-2019-9453
@@ -5,6 +5,7 @@ Notes:
bwh> Apparently introduced in 3.8 when f2fs was added.
Bugs:
upstream: released (5.2-rc1) [2777e654371dd4207a3a7f4fb5fa39550053a080]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.53) [ae3787d433f7b87ebf6b916e524c6e280e4e5804]
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "f2fs is not supportable"
diff --git a/active/CVE-2019-kvm-guest-xcr0 b/active/CVE-2019-kvm-guest-xcr0
index 440fbecf2..0afd0eae0 100644
--- a/active/CVE-2019-kvm-guest-xcr0
+++ b/active/CVE-2019-kvm-guest-xcr0
@@ -10,6 +10,7 @@ Notes:
carnil> older need to account for that.
Bugs:
upstream: released (5.1-rc6) [1811d979c71621aafc7b879477202d286f7e863b]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.73) [7a74d806bdaa4718b96577068fe86fcdb91436e1]
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2020-0030 b/active/CVE-2020-0030
index 77d99067f..47dfb2a2d 100644
--- a/active/CVE-2020-0030
+++ b/active/CVE-2020-0030
@@ -10,6 +10,7 @@ Notes:
carnil> branch
Bugs:
upstream: released (4.16-rc3) [5eeb2ca02a2f6084fc57ae5c244a38baab07033a]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: N/A "Fixed before branching point"
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "Too difficult and risky to backport"
diff --git a/active/CVE-2020-0067 b/active/CVE-2020-0067
index 54b5aba6e..eed125d30 100644
--- a/active/CVE-2020-0067
+++ b/active/CVE-2020-0067
@@ -4,6 +4,7 @@ References:
Notes:
Bugs:
upstream: released (5.5-rc1) [688078e7f36c293dae25b338ddc9e0a2790f6e06]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.119) [ed523cbd4a6594edf123dc03ec9d70ea4f793671]
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "f2fs is not supportable"
diff --git a/active/CVE-2020-11725 b/active/CVE-2020-11725
index d84fc4711..1ff5ceb16 100644
--- a/active/CVE-2020-11725
+++ b/active/CVE-2020-11725
@@ -8,6 +8,7 @@ Notes:
carnil> has been disputed to be correct by Takashi Iwai.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2020-14304 b/active/CVE-2020-14304
index 09aa7bf0c..e7b7ed552 100644
--- a/active/CVE-2020-14304
+++ b/active/CVE-2020-14304
@@ -6,6 +6,7 @@ Notes:
Bugs:
https://bugs.debian.org/960702
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
3.16-upstream-stable: ignored "EOL"
diff --git a/active/CVE-2020-16119 b/active/CVE-2020-16119
index daf316d19..7170f9e8d 100644
--- a/active/CVE-2020-16119
+++ b/active/CVE-2020-16119
@@ -8,6 +8,7 @@ Notes:
carnil> backported as well to various stable series as e.g. 4.9.108).
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: needed
diff --git a/active/CVE-2020-16120 b/active/CVE-2020-16120
index fb8cd0f8c..d1874b4fb 100644
--- a/active/CVE-2020-16120
+++ b/active/CVE-2020-16120
@@ -16,6 +16,7 @@ Notes:
bwh> run-time configuration knobs to enable these.
Bugs:
upstream: released (5.8-rc1) [48bd024b8a40d73ad6b086de2615738da0c7004f, 56230d956739b9cb1cbde439d76227d77979a04d, 05acefb4872dae89e772729efb194af754c877e8]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: N/A "Vulnerable configuration not possible"
4.9-upstream-stable: N/A "Vulnerable configuration not possible"
sid: released (5.8.7-1)
diff --git a/active/CVE-2020-25639 b/active/CVE-2020-25639
index d4b34fd7d..d00361a01 100644
--- a/active/CVE-2020-25639
+++ b/active/CVE-2020-25639
@@ -9,6 +9,7 @@ Notes:
carnil> earlier versions are not affected.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: N/A "Vulnerable code introduced later"
4.9-upstream-stable: N/A "Vulnerable code introduced later"
sid: needed
diff --git a/active/CVE-2020-25670 b/active/CVE-2020-25670
index 778f6249e..e2dbeff9a 100644
--- a/active/CVE-2020-25670
+++ b/active/CVE-2020-25670
@@ -5,6 +5,7 @@ Notes:
bwh> Not sure how far back this goes, but 4.9 seems to have the issue
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: needed
diff --git a/active/CVE-2020-25671 b/active/CVE-2020-25671
index c636288ee..13327aea2 100644
--- a/active/CVE-2020-25671
+++ b/active/CVE-2020-25671
@@ -5,6 +5,7 @@ Notes:
bwh> Not sure how far back this goes, but 4.9 seems to have the issue
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: needed
diff --git a/active/CVE-2020-25672 b/active/CVE-2020-25672
index 2191d25bf..cea0854f1 100644
--- a/active/CVE-2020-25672
+++ b/active/CVE-2020-25672
@@ -5,6 +5,7 @@ Notes:
bwh> Not sure how far back this goes, but 4.9 seems to have the issue
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: needed
diff --git a/active/CVE-2020-25673 b/active/CVE-2020-25673
index b7f85f234..882cd5b38 100644
--- a/active/CVE-2020-25673
+++ b/active/CVE-2020-25673
@@ -5,6 +5,7 @@ Notes:
bwh> Not sure how far back this goes, but 4.9 seems to have the issue
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: needed
diff --git a/active/CVE-2020-26541 b/active/CVE-2020-26541
index 69bce2496..7d5dc2d13 100644
--- a/active/CVE-2020-26541
+++ b/active/CVE-2020-26541
@@ -7,6 +7,7 @@ Notes:
bwh> UEFI Secure Boot key store and/or are themselves signed.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: N/A "Secure Boot key import not supported"
4.9-upstream-stable: N/A "Secure Boot key import not supported"
sid: needed
diff --git a/active/CVE-2020-27815 b/active/CVE-2020-27815
index f9bc8188c..bd853f880 100644
--- a/active/CVE-2020-27815
+++ b/active/CVE-2020-27815
@@ -11,6 +11,7 @@ Notes:
bwh> larger array.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: needed
diff --git a/active/CVE-2020-27820 b/active/CVE-2020-27820
index 8ec005955..cb6972cb2 100644
--- a/active/CVE-2020-27820
+++ b/active/CVE-2020-27820
@@ -9,6 +9,7 @@ Notes:
bwh> worthwhile fix anyway.
Bugs:
upstream: needed
+5.10-upstream-stable: needed
4.19-upstream-stable:
4.9-upstream-stable:
sid: needed
diff --git a/active/CVE-2020-27830 b/active/CVE-2020-27830
index b0365e0ad..cbc8c2a1d 100644
--- a/active/CVE-2020-27830
+++ b/active/CVE-2020-27830
@@ -7,6 +7,7 @@ Notes:
bwh> tty-based comms functions".
Bugs:
upstream: released (5.10-rc7) [f0992098cadb4c9c6a00703b66cafe604e178fea]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.163) [de867367f35237729e285ff6efa3fd4e4b0b9008]
4.9-upstream-stable: N/A "Vulnerability introduced later"
sid: pending (5.9.15-1)
diff --git a/active/CVE-2020-27835 b/active/CVE-2020-27835
index fa0807eda..bfe254c05 100644
--- a/active/CVE-2020-27835
+++ b/active/CVE-2020-27835
@@ -5,6 +5,7 @@ Notes:
carnil> Fixed as well in 5.9.12.
Bugs:
upstream: released (5.10-rc6) [3d2a9d642512c21a12d19b9250e7a835dcb41a79]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: pending (5.9.15-1)
diff --git a/active/CVE-2020-28588 b/active/CVE-2020-28588
index ffd27efdf..ef21eb4b3 100644
--- a/active/CVE-2020-28588
+++ b/active/CVE-2020-28588
@@ -7,6 +7,7 @@ Notes:
carnil> v5.9.y.
Bugs:
upstream: released (5.10-rc7) [4f134b89a24b965991e7c345b9a4591821f7c2a6]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: N/A "Vulnerable code not present"
4.9-upstream-stable: N/A "Vulnerable code not present"
sid: pending (5.9.15-1)
diff --git a/active/CVE-2020-29374 b/active/CVE-2020-29374
index d26482a49..1853d8f8b 100644
--- a/active/CVE-2020-29374
+++ b/active/CVE-2020-29374
@@ -5,6 +5,7 @@ Notes:
bwh> The issue is said to go back to "2.x kernels"
Bugs:
upstream: released (5.8-rc1) [17839856fd588f4ab6b789f482ed3ffd7c403e1f]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: released (5.7.6-1)
diff --git a/active/CVE-2020-29568 b/active/CVE-2020-29568
index 9cef42981..6e5dd8c60 100644
--- a/active/CVE-2020-29568
+++ b/active/CVE-2020-29568
@@ -6,6 +6,7 @@ Notes:
Bugs:
upstream: pending [fed1755b118147721f2c87b37b9d66e62c39b668, 2e85d32b1c865bec703ce0c962221a5e955c52c2, be987200fbaceaef340872841d4f7af2c5ee8dc3, 3dc86ca6b4c8cfcba9da7996189d1b5a358a94fc, 9996bd494794a2fe393e97e7a982388c6249aa76]
5.10-upstream-stable: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: pending (5.9.15-1) [bugfix/all/xen-xenbus-Allow-watches-discard-events-before-queue.patch, bugfix/all/xen-xenbus-Add-will_handle-callback-support-in-xenbu.patch, bugfix/all/xen-xenbus-xen_bus_type-Support-will_handle-watch-ca.patch, bugfix/all/xen-xenbus-Count-pending-messages-for-each-watch.patch, bugfix/all/xenbus-xenbus_backend-Disallow-pending-watch-message.patch]
diff --git a/active/CVE-2020-29569 b/active/CVE-2020-29569
index bd825ecfd..07bce197f 100644
--- a/active/CVE-2020-29569
+++ b/active/CVE-2020-29569
@@ -9,6 +9,7 @@ Notes:
Bugs:
upstream: pending [1c728719a4da6e654afb9cc047164755072ed7c9]
5.10-upstream-stable: needed
+5.10-upstream-stable: needed
4.19-upstream-stable: needed
4.9-upstream-stable: needed
sid: pending (5.9.15-1) [bugfix/all/xen-blkback-set-ring-xenblkd-to-NULL-after-kthread_s.patch]
diff --git a/active/CVE-2020-29660 b/active/CVE-2020-29660
index be131e633..0b6181344 100644
--- a/active/CVE-2020-29660
+++ b/active/CVE-2020-29660
@@ -4,6 +4,7 @@ Notes:
carnil> Fixed as well in 5.9.14.
Bugs:
upstream: released (5.10-rc7) [c8bcd9c5be24fb9e6132e97da5a35e55a83e36b9]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.163) [361e822b7d8a9d06d88f7cea0fdb0fb6e41c4d45]
4.9-upstream-stable: released (4.9.248) [ac28e357fe00902bbc21655eaee6b56c850f80af]
sid: pending (5.9.15-1)
diff --git a/active/CVE-2020-29661 b/active/CVE-2020-29661
index 4601148da..e4c985b98 100644
--- a/active/CVE-2020-29661
+++ b/active/CVE-2020-29661
@@ -4,6 +4,7 @@ Notes:
carnil> Fixed as well in 5.9.14.
Bugs:
upstream: released (5.10-rc7) [54ffccbf053b5b6ca4f6e45094b942fab92a25fc]
+5.10-upstream-stable: N/A "Fixed before branch point"
4.19-upstream-stable: released (4.19.163) [13f10a78097df2f14d4e1fd390dbaa3e28502ca7]
4.9-upstream-stable: released (4.9.248) [742f3062298ac1ae1d28de31b1f946f93db1eba1]
sid: pending (5.9.15-1)

© 2014-2024 Faster IT GmbH | imprint | privacy policy