retire issues

4 files changed, 0 insertions, 72 deletions

diff --git a/active/CVE-2019-2213 b/active/CVE-2019-2213
deleted file mode 100644
index 55b84056..00000000
--- a/active/CVE-2019-2213
+++ /dev/null
@@ -1,21 +0,0 @@
-Description: binder: fix possible UAF when freeing buffer
-References:
- https://lore.kernel.org/patchwork/patch/1087916/
-Notes:
- bwh> For branches older than 4.20, the second hunk should be applied
- bwh> to binder_thread_write() instead of binder_free_buf().
- bwh> For branches older than 4.14, the first hunk should be applied to
- bwh> binder_pop_transaction() instead of binder_free_transaction().
- bwh> It's not clear how the locking should be done for branches older
- 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"
-sid: released (5.2.6-1)
-5.10-bullseye-security: N/A "Fixed before branching point"
-4.19-buster-security: released (4.19.67-1)
-4.9-stretch-security: ignored "EOL"
-3.16-jessie-security: ignored "Android drivers not supported"
diff --git a/active/CVE-2019-9245 b/active/CVE-2019-9245
deleted file mode 100644
index c674330b..00000000
--- a/active/CVE-2019-9245
+++ /dev/null
@@ -1,15 +0,0 @@
-Description: f2fs: sanity check of xattr entry size
-References:
-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"
-sid: released (4.19.16-1)
-5.10-bullseye-security: N/A "Fixed before branching point"
-4.19-buster-security: N/A "Fixed before branching point"
-4.9-stretch-security: ignored "f2fs is not supportable"
-3.16-jessie-security: ignored "f2fs is not supportable"
diff --git a/active/CVE-2019-kvm-guest-xcr0 b/active/CVE-2019-kvm-guest-xcr0
deleted file mode 100644
index 8bc98b6d..00000000
--- a/active/CVE-2019-kvm-guest-xcr0
+++ /dev/null
@@ -1,21 +0,0 @@
-Description: KVM guest's XCR0 is used in host after MCE
-References:
-Notes:
- bwh> Branches before 4.14 should probably apply commit b060ca3b2e9e
- bwh> "kvm: vmx: Handle VMLAUNCH/VMRESUME failure properly" first, if
- bwh> only to avoid conflicts.  But this in turn needs further fixes.
- carnil> In a821bab2d1ee ("KVM: VMX: Move VMX specific files to a "vmx"
- carnil> subdirectory") in 5.0-rc1 file arch/x86/kvm/vmx.c was moved to
- carnil> subdirectory arch/x86/kvm/vmx/vmx.c so backport to 4.19 and
- 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"
-sid: released (5.2.6-1)
-5.10-bullseye-security: N/A "Fixed before branching point"
-4.19-buster-security: released (4.19.87-1)
-4.9-stretch-security: ignored "EOL"
-3.16-jessie-security: ignored "EOL"
diff --git a/active/CVE-2020-0067 b/active/CVE-2020-0067
deleted file mode 100644
index 2c83195f..00000000
--- a/active/CVE-2020-0067
+++ /dev/null
@@ -1,15 +0,0 @@
-Description: f2fs: fix to avoid memory leakage in f2fs_listxattr
-References:
- https://source.android.com/security/bulletin/pixel/2020-04-01
-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"
-sid: released (5.5.13-1)
-5.10-bullseye-security: N/A "Fixed before branching point"
-4.19-buster-security: released (4.19.118-1) [bugfix/all/f2fs-fix-to-avoid-memory-leakage-in-f2fs_listxattr.patch]
-4.9-stretch-security: ignored "f2fs is not supportable"
-3.16-jessie-security: ignored "f2fs is not supportable"