From 30e923c9029fa0f9ba1976670c8ee73cbf02169e Mon Sep 17 00:00:00 2001 From: Salvatore Bonaccorso Date: Sun, 9 Feb 2020 21:22:45 +0100 Subject: Retire some CVEs --- active/CVE-2018-20976 | 12 ------------ active/CVE-2018-21008 | 13 ------------- active/CVE-2018-ebpf-filter-dos | 13 ------------- active/CVE-2019-0136 | 20 -------------------- active/CVE-2019-10220 | 23 ----------------------- active/CVE-2019-14814 | 16 ---------------- active/CVE-2019-14815 | 20 -------------------- active/CVE-2019-14816 | 16 ---------------- active/CVE-2019-14895 | 18 ------------------ active/CVE-2019-15030 | 20 -------------------- active/CVE-2019-15031 | 18 ------------------ active/CVE-2019-15098 | 16 ---------------- active/CVE-2019-15099 | 15 --------------- active/CVE-2019-15217 | 15 --------------- active/CVE-2019-15291 | 13 ------------- active/CVE-2019-15504 | 16 ---------------- active/CVE-2019-15505 | 16 ---------------- active/CVE-2019-15917 | 15 --------------- active/CVE-2019-15918 | 14 -------------- active/CVE-2019-16714 | 13 ------------- active/CVE-2019-16746 | 13 ------------- active/CVE-2019-17052 | 12 ------------ active/CVE-2019-17053 | 12 ------------ active/CVE-2019-17054 | 12 ------------ active/CVE-2019-17055 | 12 ------------ active/CVE-2019-17056 | 12 ------------ active/CVE-2019-17075 | 15 --------------- active/CVE-2019-17133 | 14 -------------- active/CVE-2019-17666 | 13 ------------- active/CVE-2019-18282 | 15 --------------- active/CVE-2019-18660 | 17 ----------------- active/CVE-2019-18683 | 15 --------------- active/CVE-2019-18786 | 15 --------------- active/CVE-2019-18806 | 16 ---------------- active/CVE-2019-18809 | 17 ----------------- active/CVE-2019-18813 | 15 --------------- active/CVE-2019-19037 | 18 ------------------ active/CVE-2019-19045 | 13 ------------- active/CVE-2019-19048 | 14 -------------- active/CVE-2019-19052 | 14 -------------- active/CVE-2019-19056 | 15 --------------- active/CVE-2019-19057 | 15 --------------- active/CVE-2019-19058 | 14 -------------- active/CVE-2019-19059 | 14 -------------- active/CVE-2019-19062 | 16 ---------------- active/CVE-2019-19065 | 14 -------------- active/CVE-2019-19066 | 14 -------------- active/CVE-2019-19068 | 15 --------------- active/CVE-2019-19071 | 16 ---------------- active/CVE-2019-19077 | 14 -------------- active/CVE-2019-19078 | 15 --------------- active/CVE-2019-19079 | 14 -------------- active/CVE-2019-19080 | 14 -------------- active/CVE-2019-19081 | 14 -------------- active/CVE-2019-19227 | 12 ------------ active/CVE-2019-19332 | 15 --------------- active/CVE-2019-19523 | 13 ------------- active/CVE-2019-19524 | 13 ------------- active/CVE-2019-19525 | 13 ------------- active/CVE-2019-19526 | 15 --------------- active/CVE-2019-19527 | 14 -------------- active/CVE-2019-19528 | 16 ---------------- active/CVE-2019-19529 | 15 --------------- active/CVE-2019-19530 | 13 ------------- active/CVE-2019-19531 | 13 ------------- active/CVE-2019-19532 | 13 ------------- active/CVE-2019-19533 | 13 ------------- active/CVE-2019-19534 | 13 ------------- active/CVE-2019-19535 | 15 --------------- active/CVE-2019-19536 | 13 ------------- active/CVE-2019-19537 | 13 ------------- active/CVE-2019-19767 | 16 ---------------- active/CVE-2019-19922 | 18 ------------------ active/CVE-2019-19965 | 15 --------------- active/CVE-2019-20096 | 12 ------------ active/CVE-2019-2215 | 15 --------------- retired/CVE-2018-20976 | 12 ++++++++++++ retired/CVE-2018-21008 | 13 +++++++++++++ retired/CVE-2018-ebpf-filter-dos | 13 +++++++++++++ retired/CVE-2019-0136 | 20 ++++++++++++++++++++ retired/CVE-2019-10220 | 23 +++++++++++++++++++++++ retired/CVE-2019-14814 | 16 ++++++++++++++++ retired/CVE-2019-14815 | 20 ++++++++++++++++++++ retired/CVE-2019-14816 | 16 ++++++++++++++++ retired/CVE-2019-14895 | 18 ++++++++++++++++++ retired/CVE-2019-15030 | 20 ++++++++++++++++++++ retired/CVE-2019-15031 | 18 ++++++++++++++++++ retired/CVE-2019-15098 | 16 ++++++++++++++++ retired/CVE-2019-15099 | 15 +++++++++++++++ retired/CVE-2019-15217 | 15 +++++++++++++++ retired/CVE-2019-15291 | 13 +++++++++++++ retired/CVE-2019-15504 | 16 ++++++++++++++++ retired/CVE-2019-15505 | 16 ++++++++++++++++ retired/CVE-2019-15917 | 15 +++++++++++++++ retired/CVE-2019-15918 | 14 ++++++++++++++ retired/CVE-2019-16714 | 13 +++++++++++++ retired/CVE-2019-16746 | 13 +++++++++++++ retired/CVE-2019-17052 | 12 ++++++++++++ retired/CVE-2019-17053 | 12 ++++++++++++ retired/CVE-2019-17054 | 12 ++++++++++++ retired/CVE-2019-17055 | 12 ++++++++++++ retired/CVE-2019-17056 | 12 ++++++++++++ retired/CVE-2019-17075 | 15 +++++++++++++++ retired/CVE-2019-17133 | 14 ++++++++++++++ retired/CVE-2019-17666 | 13 +++++++++++++ retired/CVE-2019-18282 | 15 +++++++++++++++ retired/CVE-2019-18660 | 17 +++++++++++++++++ retired/CVE-2019-18683 | 15 +++++++++++++++ retired/CVE-2019-18786 | 15 +++++++++++++++ retired/CVE-2019-18806 | 16 ++++++++++++++++ retired/CVE-2019-18809 | 17 +++++++++++++++++ retired/CVE-2019-18813 | 15 +++++++++++++++ retired/CVE-2019-19037 | 18 ++++++++++++++++++ retired/CVE-2019-19045 | 13 +++++++++++++ retired/CVE-2019-19048 | 14 ++++++++++++++ retired/CVE-2019-19052 | 14 ++++++++++++++ retired/CVE-2019-19056 | 15 +++++++++++++++ retired/CVE-2019-19057 | 15 +++++++++++++++ retired/CVE-2019-19058 | 14 ++++++++++++++ retired/CVE-2019-19059 | 14 ++++++++++++++ retired/CVE-2019-19062 | 16 ++++++++++++++++ retired/CVE-2019-19065 | 14 ++++++++++++++ retired/CVE-2019-19066 | 14 ++++++++++++++ retired/CVE-2019-19068 | 15 +++++++++++++++ retired/CVE-2019-19071 | 16 ++++++++++++++++ retired/CVE-2019-19077 | 14 ++++++++++++++ retired/CVE-2019-19078 | 15 +++++++++++++++ retired/CVE-2019-19079 | 14 ++++++++++++++ retired/CVE-2019-19080 | 14 ++++++++++++++ retired/CVE-2019-19081 | 14 ++++++++++++++ retired/CVE-2019-19227 | 12 ++++++++++++ retired/CVE-2019-19332 | 15 +++++++++++++++ retired/CVE-2019-19523 | 13 +++++++++++++ retired/CVE-2019-19524 | 13 +++++++++++++ retired/CVE-2019-19525 | 13 +++++++++++++ retired/CVE-2019-19526 | 15 +++++++++++++++ retired/CVE-2019-19527 | 14 ++++++++++++++ retired/CVE-2019-19528 | 16 ++++++++++++++++ retired/CVE-2019-19529 | 15 +++++++++++++++ retired/CVE-2019-19530 | 13 +++++++++++++ retired/CVE-2019-19531 | 13 +++++++++++++ retired/CVE-2019-19532 | 13 +++++++++++++ retired/CVE-2019-19533 | 13 +++++++++++++ retired/CVE-2019-19534 | 13 +++++++++++++ retired/CVE-2019-19535 | 15 +++++++++++++++ retired/CVE-2019-19536 | 13 +++++++++++++ retired/CVE-2019-19537 | 13 +++++++++++++ retired/CVE-2019-19767 | 16 ++++++++++++++++ retired/CVE-2019-19922 | 18 ++++++++++++++++++ retired/CVE-2019-19965 | 15 +++++++++++++++ retired/CVE-2019-20096 | 12 ++++++++++++ retired/CVE-2019-2215 | 15 +++++++++++++++ 152 files changed, 1118 insertions(+), 1118 deletions(-) delete mode 100644 active/CVE-2018-20976 delete mode 100644 active/CVE-2018-21008 delete mode 100644 active/CVE-2018-ebpf-filter-dos delete mode 100644 active/CVE-2019-0136 delete mode 100644 active/CVE-2019-10220 delete mode 100644 active/CVE-2019-14814 delete mode 100644 active/CVE-2019-14815 delete mode 100644 active/CVE-2019-14816 delete mode 100644 active/CVE-2019-14895 delete mode 100644 active/CVE-2019-15030 delete mode 100644 active/CVE-2019-15031 delete mode 100644 active/CVE-2019-15098 delete mode 100644 active/CVE-2019-15099 delete mode 100644 active/CVE-2019-15217 delete mode 100644 active/CVE-2019-15291 delete mode 100644 active/CVE-2019-15504 delete mode 100644 active/CVE-2019-15505 delete mode 100644 active/CVE-2019-15917 delete mode 100644 active/CVE-2019-15918 delete mode 100644 active/CVE-2019-16714 delete mode 100644 active/CVE-2019-16746 delete mode 100644 active/CVE-2019-17052 delete mode 100644 active/CVE-2019-17053 delete mode 100644 active/CVE-2019-17054 delete mode 100644 active/CVE-2019-17055 delete mode 100644 active/CVE-2019-17056 delete mode 100644 active/CVE-2019-17075 delete mode 100644 active/CVE-2019-17133 delete mode 100644 active/CVE-2019-17666 delete mode 100644 active/CVE-2019-18282 delete mode 100644 active/CVE-2019-18660 delete mode 100644 active/CVE-2019-18683 delete mode 100644 active/CVE-2019-18786 delete mode 100644 active/CVE-2019-18806 delete mode 100644 active/CVE-2019-18809 delete mode 100644 active/CVE-2019-18813 delete mode 100644 active/CVE-2019-19037 delete mode 100644 active/CVE-2019-19045 delete mode 100644 active/CVE-2019-19048 delete mode 100644 active/CVE-2019-19052 delete mode 100644 active/CVE-2019-19056 delete mode 100644 active/CVE-2019-19057 delete mode 100644 active/CVE-2019-19058 delete mode 100644 active/CVE-2019-19059 delete mode 100644 active/CVE-2019-19062 delete mode 100644 active/CVE-2019-19065 delete mode 100644 active/CVE-2019-19066 delete mode 100644 active/CVE-2019-19068 delete mode 100644 active/CVE-2019-19071 delete mode 100644 active/CVE-2019-19077 delete mode 100644 active/CVE-2019-19078 delete mode 100644 active/CVE-2019-19079 delete mode 100644 active/CVE-2019-19080 delete mode 100644 active/CVE-2019-19081 delete mode 100644 active/CVE-2019-19227 delete mode 100644 active/CVE-2019-19332 delete mode 100644 active/CVE-2019-19523 delete mode 100644 active/CVE-2019-19524 delete mode 100644 active/CVE-2019-19525 delete mode 100644 active/CVE-2019-19526 delete mode 100644 active/CVE-2019-19527 delete mode 100644 active/CVE-2019-19528 delete mode 100644 active/CVE-2019-19529 delete mode 100644 active/CVE-2019-19530 delete mode 100644 active/CVE-2019-19531 delete mode 100644 active/CVE-2019-19532 delete mode 100644 active/CVE-2019-19533 delete mode 100644 active/CVE-2019-19534 delete mode 100644 active/CVE-2019-19535 delete mode 100644 active/CVE-2019-19536 delete mode 100644 active/CVE-2019-19537 delete mode 100644 active/CVE-2019-19767 delete mode 100644 active/CVE-2019-19922 delete mode 100644 active/CVE-2019-19965 delete mode 100644 active/CVE-2019-20096 delete mode 100644 active/CVE-2019-2215 create mode 100644 retired/CVE-2018-20976 create mode 100644 retired/CVE-2018-21008 create mode 100644 retired/CVE-2018-ebpf-filter-dos create mode 100644 retired/CVE-2019-0136 create mode 100644 retired/CVE-2019-10220 create mode 100644 retired/CVE-2019-14814 create mode 100644 retired/CVE-2019-14815 create mode 100644 retired/CVE-2019-14816 create mode 100644 retired/CVE-2019-14895 create mode 100644 retired/CVE-2019-15030 create mode 100644 retired/CVE-2019-15031 create mode 100644 retired/CVE-2019-15098 create mode 100644 retired/CVE-2019-15099 create mode 100644 retired/CVE-2019-15217 create mode 100644 retired/CVE-2019-15291 create mode 100644 retired/CVE-2019-15504 create mode 100644 retired/CVE-2019-15505 create mode 100644 retired/CVE-2019-15917 create mode 100644 retired/CVE-2019-15918 create mode 100644 retired/CVE-2019-16714 create mode 100644 retired/CVE-2019-16746 create mode 100644 retired/CVE-2019-17052 create mode 100644 retired/CVE-2019-17053 create mode 100644 retired/CVE-2019-17054 create mode 100644 retired/CVE-2019-17055 create mode 100644 retired/CVE-2019-17056 create mode 100644 retired/CVE-2019-17075 create mode 100644 retired/CVE-2019-17133 create mode 100644 retired/CVE-2019-17666 create mode 100644 retired/CVE-2019-18282 create mode 100644 retired/CVE-2019-18660 create mode 100644 retired/CVE-2019-18683 create mode 100644 retired/CVE-2019-18786 create mode 100644 retired/CVE-2019-18806 create mode 100644 retired/CVE-2019-18809 create mode 100644 retired/CVE-2019-18813 create mode 100644 retired/CVE-2019-19037 create mode 100644 retired/CVE-2019-19045 create mode 100644 retired/CVE-2019-19048 create mode 100644 retired/CVE-2019-19052 create mode 100644 retired/CVE-2019-19056 create mode 100644 retired/CVE-2019-19057 create mode 100644 retired/CVE-2019-19058 create mode 100644 retired/CVE-2019-19059 create mode 100644 retired/CVE-2019-19062 create mode 100644 retired/CVE-2019-19065 create mode 100644 retired/CVE-2019-19066 create mode 100644 retired/CVE-2019-19068 create mode 100644 retired/CVE-2019-19071 create mode 100644 retired/CVE-2019-19077 create mode 100644 retired/CVE-2019-19078 create mode 100644 retired/CVE-2019-19079 create mode 100644 retired/CVE-2019-19080 create mode 100644 retired/CVE-2019-19081 create mode 100644 retired/CVE-2019-19227 create mode 100644 retired/CVE-2019-19332 create mode 100644 retired/CVE-2019-19523 create mode 100644 retired/CVE-2019-19524 create mode 100644 retired/CVE-2019-19525 create mode 100644 retired/CVE-2019-19526 create mode 100644 retired/CVE-2019-19527 create mode 100644 retired/CVE-2019-19528 create mode 100644 retired/CVE-2019-19529 create mode 100644 retired/CVE-2019-19530 create mode 100644 retired/CVE-2019-19531 create mode 100644 retired/CVE-2019-19532 create mode 100644 retired/CVE-2019-19533 create mode 100644 retired/CVE-2019-19534 create mode 100644 retired/CVE-2019-19535 create mode 100644 retired/CVE-2019-19536 create mode 100644 retired/CVE-2019-19537 create mode 100644 retired/CVE-2019-19767 create mode 100644 retired/CVE-2019-19922 create mode 100644 retired/CVE-2019-19965 create mode 100644 retired/CVE-2019-20096 create mode 100644 retired/CVE-2019-2215 diff --git a/active/CVE-2018-20976 b/active/CVE-2018-20976 deleted file mode 100644 index 0ebf974f..00000000 --- a/active/CVE-2018-20976 +++ /dev/null @@ -1,12 +0,0 @@ -Description: xfs: clear sb->s_fs_info on mount failure -References: -Notes: -Bugs: -upstream: released (4.18-rc1) [c9fbd7bbc23dbdd73364be4d045e5d3612cf6e82] -4.19-upstream-stable: N/A "Fixed before branching point" -4.9-upstream-stable: released (4.9.197) [e6e3f36b1ac9c439d3bc0b2c2aaf1663ad705ac0] -3.16-upstream-stable: released (3.16.74) [bf3878994377a97143f5f6b6e60a18f9b76e0476] -sid: released (4.18.6-1) -4.19-buster-security: N/A "Fixed before branching point" -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.74-1) diff --git a/active/CVE-2018-21008 b/active/CVE-2018-21008 deleted file mode 100644 index 11f060a4..00000000 --- a/active/CVE-2018-21008 +++ /dev/null @@ -1,13 +0,0 @@ -Description: rsi: add fix for crash during assertions -References: -Notes: - bwh> Apparently introduced in 3.15 when rsi driver was added. -Bugs: -upstream: released (4.18-rc1) [abd39c6ded9db53aa44c2540092bdd5fb6590fa8] -4.19-upstream-stable: N/A "Fixed before branching point" -4.9-upstream-stable: released (4.9.211) [65b32fd4eabc5209019894627b1bda65611fd1cb] -3.16-upstream-stable: released (3.16.74) [fd56118648c89adbd7a64bc8e3e26ac4871d1c1a] -sid: released (4.18.6-1) -4.19-buster-security: N/A "Fixed before branching point" -4.9-stretch-security: released (4.9.210-1) [bugfix/all/rsi-add-fix-for-crash-during-assertions.patch] -3.16-jessie-security: released (3.16.74-1) diff --git a/active/CVE-2018-ebpf-filter-dos b/active/CVE-2018-ebpf-filter-dos deleted file mode 100644 index 20753e96..00000000 --- a/active/CVE-2018-ebpf-filter-dos +++ /dev/null @@ -1,13 +0,0 @@ -Description: Ability to fill entire module space with eBPF JIT socket filters -References: -Notes: - bwh> This should be minor for Debian because we don't enable JIT by default. -Bugs: -upstream: released (4.20-rc1) [ede95a63b5e84ddeea6b0c473b36ab8bfd8c6ce3] -4.19-upstream-stable: released (4.19.47) [43caa29c99db5a41b204e8ced01b00e151335ca8] -4.9-upstream-stable: released (4.9.190) [c98446e1bab6253ddce7144cc2a91c400a323839] -3.16-upstream-stable: N/A "eBPF not implemented" -sid: released (5.2.6-1) -4.19-buster-security: released (4.19.67-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "eBPF not implemented" diff --git a/active/CVE-2019-0136 b/active/CVE-2019-0136 deleted file mode 100644 index d8fa5a9e..00000000 --- a/active/CVE-2019-0136 +++ /dev/null @@ -1,20 +0,0 @@ -Description: Insufficient access control in the Intel(R) PROSet/Wireless WiFi Software driver before version 21.10 may allow an unauthenticated user to potentially enable denial of service via adjacent access. -References: - https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-0136.html -Notes: - carnil> the second commit 79c92ca42b5a ("mac80211: handle - carnil> deauthentication/disassociation from TDLS peer") is not applied - carnil> to older branches and might need investigation if applicable. - bwh> I think commit 79c92ca42b5a is relevant to older branches and have - bwh> backported it to 3.16. - carnil> Backport request for 4.9: https://lore.kernel.org/stable/20190927115711.GA8961@eldamar.local/ - bwh> stretch still only has the first commit. -Bugs: -upstream: released (v5.2-rc6) [588f7d39b3592a36fb7702ae3b8bdd9be4621e2f, 79c92ca42b5a3e0ea172ea2ce8df8e125af237da] -4.19-upstream-stable: released (4.19.56) [0e879ef1cb5baddebe1f12a9a3940a87d8e61558, 1e1007ac47d85dacf6d45821a2870b6268499700] -4.9-upstream-stable: released (4.9.195) [9f0f5ff93ed0205a90f11103e9937f3c0417cd4b, 7b1f4ffab73d9319b8132bbf5f4a0e2110a98bde] -3.16-upstream-stable: released (3.16.74) [62909f7d0b1360ddb147bae8f546228dd93588e1, 8c2981482a9a1b8910dd0b4365b53db1a056ae66] -sid: released (5.2.6-1) -4.19-buster-security: released (4.19.67-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.74-1) diff --git a/active/CVE-2019-10220 b/active/CVE-2019-10220 deleted file mode 100644 index be260f16..00000000 --- a/active/CVE-2019-10220 +++ /dev/null @@ -1,23 +0,0 @@ -Description: CIFS: Relative paths injection in directory entry lists -References: - https://bugzilla.redhat.com/show_bug.cgi?id=1741727 - https://bugzilla.suse.com/show_bug.cgi?id=1144903 - https://bugzilla.samba.org/show_bug.cgi?id=14072 -Notes: - carnil> Needed a followup c512c6918719 ("uaccess: implement a proper - carnil> unsafe_copy_to_user() and switch filldir over to it"), cf. - carnil> https://lore.kernel.org/linux-fsdevel/20191006222046.GA18027@roeck-us.net/ - carnil> which landed in 5.4-rc3. - bwh> Although this was reported against CIFS, it seems to be a general - bwh> vulnerability for all filesystems dealing with untrusted servers or - bwh> storage. Thankfully the fix is also general. - bwh> The changes to uaccess in filldir are *not* required. -Bugs: -upstream: released (5.4-rc4) [8a23eb804ca4f2be909e372cf5a9e7b30ae476cd, b9959c7a347d6adbb558fba7e36e9fef3cba3b07] -4.19-upstream-stable: released (4.19.93) [40696eb2bce798c4764886fbc576426bd5c4cc3c, 0643c3d694ad9f1e5cb0bc7a487bf9f86a5eaf75] -4.9-upstream-stable: released (4.9.208) [89f58402e7088d38365f227a7943b1b3fed7489b, 1944687187713590a8722f3f1dfd1cd90e7cbde6] -3.16-upstream-stable: released (3.16.81) [8b85eda7dac918a308e6e1d9137887930e80827a, 0ad70158f3c02e373e17377237b85e43f06d6752] -sid: released (5.3.9-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-14814 b/active/CVE-2019-14814 deleted file mode 100644 index 4774f8c0..00000000 --- a/active/CVE-2019-14814 +++ /dev/null @@ -1,16 +0,0 @@ -Description: Heap Overflow in mwifiex_set_uap_rates() function -References: - https://www.openwall.com/lists/oss-security/2019/08/28/1 - https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@gmail.com/ -Notes: - bwh> Introduced in 3.7 by commit a3c2c4f6d8bc "mwifiex: parse rate info - bwh> for AP". -Bugs: -upstream: released (5.3) [7caac62ed598a196d6ddf8d9c121e12e082cac3a] -4.19-upstream-stable: released (4.19.75) [941431c491a68e0428bdfb46bbe4cbc52f7bfabb] -4.9-upstream-stable: released (4.9.194) [21dfacaf201ed13af70a8bd3e66bcf18cdb63b35] -3.16-upstream-stable: released (3.16.74) [fb8186b15518423646f0e2105c34b3e620623b4e] -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.74-1) diff --git a/active/CVE-2019-14815 b/active/CVE-2019-14815 deleted file mode 100644 index ddeeb10f..00000000 --- a/active/CVE-2019-14815 +++ /dev/null @@ -1,20 +0,0 @@ -Description: Heap Overflow in mwifiex_set_wmm_params() function -References: - https://www.openwall.com/lists/oss-security/2019/08/28/1 - https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@gmail.com/ -Notes: - bwh> Introduced in 4.10 by commit 113630b581d6 "mwifiex: vendor_ie length - bwh> check for parse WMM IEs". - carnil> The bounds-check in mwifiex_set_wmm_paramsare still applied as - carnil> well in older versions e.g. 4.9.194. Put the state again in - carnil> needed for 4.9-stretch-security but just to recheck if this is - carnil> really not needed to track for CVE-2019-14815. -Bugs: -upstream: released (5.3) [7caac62ed598a196d6ddf8d9c121e12e082cac3a] -4.19-upstream-stable: released (4.19.75) [941431c491a68e0428bdfb46bbe4cbc52f7bfabb] -4.9-upstream-stable: released (4.9.194) [21dfacaf201ed13af70a8bd3e66bcf18cdb63b35] -3.16-upstream-stable: N/A "Vulnerability introduced later" -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/active/CVE-2019-14816 b/active/CVE-2019-14816 deleted file mode 100644 index f115d518..00000000 --- a/active/CVE-2019-14816 +++ /dev/null @@ -1,16 +0,0 @@ -Description: Heap Overflow in mwifiex_update_vs_ie() function -References: - https://www.openwall.com/lists/oss-security/2019/08/28/1 - https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@gmail.com/ -Notes: - bwh> Introduced in 3.6 by commit 2152fe9c2fa4 "mwifiex: parse WPS IEs from - bwh> beacon_data". -Bugs: -upstream: released (5.3) [7caac62ed598a196d6ddf8d9c121e12e082cac3a] -4.19-upstream-stable: released (4.19.75) [941431c491a68e0428bdfb46bbe4cbc52f7bfabb] -4.9-upstream-stable: released (4.9.194) [21dfacaf201ed13af70a8bd3e66bcf18cdb63b35] -3.16-upstream-stable: released (3.16.74) [fb8186b15518423646f0e2105c34b3e620623b4e] -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.74-1) diff --git a/active/CVE-2019-14895 b/active/CVE-2019-14895 deleted file mode 100644 index ddcce639..00000000 --- a/active/CVE-2019-14895 +++ /dev/null @@ -1,18 +0,0 @@ -Description: Heap overflow in mwifiex_process_country_ie() function of Marvell Wifi driver -References: - https://www.openwall.com/lists/oss-security/2019/11/22/1 - https://patchwork.kernel.org/patch/11256477/ -Notes: - bwh> Introduced in 3.7 by commit e89e2da29b7e "mwifiex: use country ie of - bwh> requested AP while associating". Fixed by commit 3d94a4a8373b - bwh> "mwifiex: fix possible heap overflow in mwifiex_process_country_ie()". - carnil> Fixed as well in 5.4.12. -Bugs: -upstream: released (5.5-rc3) [3d94a4a8373bf5f45cf5f939e88b8354dbf2311b] -4.19-upstream-stable: released (4.19.96) [0aa8632c57930243bea6fa4ebcbff8fac089e664] -4.9-upstream-stable: released (4.9.210) [efa99b6f3844bd20d46c8afd78f92a0161a4718e] -3.16-upstream-stable: released (3.16.81) [3b2f9bd867e1a288b470da440992a908c5972644] -sid: released (5.4.13-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-15030 b/active/CVE-2019-15030 deleted file mode 100644 index a42adc8f..00000000 --- a/active/CVE-2019-15030 +++ /dev/null @@ -1,20 +0,0 @@ -Description: powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction -References: -Notes: - carnil> Commit fixes f48e91e87e67 ("powerpc/tm: Fix FP and VMX register - carnil> corruption") but that commit was backported as well to older - carnil> versions than 4.12, so the CC to stable@v.k.o does not seem - carnil> completely correct. It was included as well in 4.9.30. - carnil> Fix can be defered to point release when updating to new - carnil> upstream stable versions as we disable - carnil> CONFIG_PPC_TRANSACTIONAL_MEM since 5.2.6-1 (sid), 4.19.67-2 - carnil> (buster) and 4.9.184-1 (stretch). -Bugs: -upstream: released (5.3-rc8) [8205d5d98ef7f155de211f5e2eb6ca03d95a5a60] -4.19-upstream-stable: released (4.19.73) [47a0f70d7d9ac3d6b1a96b312d07bc67af3834e9] -4.9-upstream-stable: released (4.9.193) [acdf558ef62ceb71938d87f5b700b7ecc0bbee90] -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-15031 b/active/CVE-2019-15031 deleted file mode 100644 index a915602f..00000000 --- a/active/CVE-2019-15031 +++ /dev/null @@ -1,18 +0,0 @@ -Description: powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts -References: - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843533 -Notes: - carnil> Commit fixes a7771176b439 ("powerpc: Don't enable FP/Altivec if - carnil> not checkpointed") in 4.15-rc1. Fix can be defered to point - carnil> release when updating to new upstream stable versions as we - carnil> disable CONFIG_PPC_TRANSACTIONAL_MEM since 5.2.6-1 (sid), - carnil> 4.19.67-2 (buster). -Bugs: -upstream: released (5.3-rc8) [a8318c13e79badb92bc6640704a64cc022a6eb97] -4.19-upstream-stable: released (4.19.73) [569775bd536416ed9049aa580d9f89a0b4307d60] -4.9-upstream-stable: N/A "Vulnerable code introduced later" -3.16-upstream-stable: N/A "Vulnerable code introduced later" -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code introduced later" -3.16-jessie-security: N/A "Vulnerable code introduced later" diff --git a/active/CVE-2019-15098 b/active/CVE-2019-15098 deleted file mode 100644 index 1c826f3b..00000000 --- a/active/CVE-2019-15098 +++ /dev/null @@ -1,16 +0,0 @@ -Description: Fix a NULL-ptr-deref bug in ath6kl_usb_alloc_urb_from_pipe -References: - https://lore.kernel.org/linux-wireless/20190804002905.11292-1-benquike@gmail.com/T/#u - https://syzkaller.appspot.com/bug?id=cd8b9cfe50a0bf36ee19eda2d7e2e06843dfbeaf -Notes: - bwh> Introduced in Linux 3.5 by commit 9cbee358687e "ath6kl: add full USB - bwh> support". -Bugs: -upstream: released (5.4-rc1) [39d170b3cb62ba98567f5c4f40c27b5864b304e5] -4.19-upstream-stable: released (4.19.82) [696da02259463ea634821e117088f82afe7bf851] -4.9-upstream-stable: released (4.9.199) [3c7f02d13b8d72dbb1dd9b0fe858459d263b1fbd] -3.16-upstream-stable: released (3.16.77) [3e8e6f9a952c9a7e0be92518906dcdb7c8d1ca29] -sid: released (5.3.7-1) [bugfix/all/ath6kl-fix-a-NULL-ptr-deref-bug-in-ath6kl_usb_alloc_.patch] -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-15099 b/active/CVE-2019-15099 deleted file mode 100644 index ed10fdc3..00000000 --- a/active/CVE-2019-15099 +++ /dev/null @@ -1,15 +0,0 @@ -Description: Fix a NULL-ptr-deref bug in ath10k_usb_alloc_urb_from_pipe -References: - https://lore.kernel.org/linux-wireless/20190804003101.11541-1-benquike@gmail.com/T/#u -Notes: - bwh> Introduced in 4.14 by commit 4db66499df91 "ath10k: add initial USB - bwh> support". -Bugs: -upstream: released (5.5-rc1) [bfd6e6e6c5d2ee43a3d9902b36e01fc7527ebb27] -4.19-upstream-stable: released (4.19.87) [f0cfe98332d650f31b462207d63c496b4cedaee2] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-15217 b/active/CVE-2019-15217 deleted file mode 100644 index 88067cdb..00000000 --- a/active/CVE-2019-15217 +++ /dev/null @@ -1,15 +0,0 @@ -Description: media: usb:zr364xx:Fix KASAN:null-ptr-deref Read in zr364xx_vidioc_querycap -References: - https://syzkaller.appspot.com/bug?id=9c0c178c24d828a7378f483309001329750aad64 -Notes: - bwh> Introduced in 2.6.32 by commit ccbf035ae5de "V4L/DVB (12278): zr364xx: - bwh> implement V4L2_CAP_STREAMING". -Bugs: -upstream: released (5.3-rc1) [5d2e73a5f80a5b5aff3caf1ec6d39b5b3f54b26e] -4.19-upstream-stable: released (4.19.97) [0648766cb7d336e5932278c316aef6aac35d60ab] -4.9-upstream-stable: released (4.9.211) [6ba34f5de2a45050729836e3d48ed10ee53d0276] -3.16-upstream-stable: released (3.16.77) [4accfbf9527ed191513f4d2d738caf15ad4e8657] -sid: released (5.2.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) [bugfix/all/media-usb-zr364xx-fix-kasan-null-ptr-deref-read-in-z.patch] -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-15291 b/active/CVE-2019-15291 deleted file mode 100644 index ebf560e8..00000000 --- a/active/CVE-2019-15291 +++ /dev/null @@ -1,13 +0,0 @@ -Description: general protection fault in flexcop_usb_probe -References: - https://syzkaller.appspot.com/bug?id=c0203bd72037d07493f4b7562411e4f5f4553a8f -Notes: -Bugs: -upstream: released (5.5-rc1) [1b976fc6d684e3282914cdbe7a8d68fdce19095c] -4.19-upstream-stable: released (4.19.87) [8b42c263ec1a348bf098e6255407486c1bf17ece] -4.9-upstream-stable: released (4.9.204) [2ab1da610f23d72ab53c3951876fa44ed85e1f99] -3.16-upstream-stable: released (3.16.79) [470a2d36f614f40b7f032071cfa6662dfcc1eda4] -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-15504 b/active/CVE-2019-15504 deleted file mode 100644 index 59b824d3..00000000 --- a/active/CVE-2019-15504 +++ /dev/null @@ -1,16 +0,0 @@ -Description: Fix a double free bug in rsi_91x_deinit -References: - https://lore.kernel.org/lkml/20190819220230.10597-1-benquike@gmail.com/ -Notes: - carnil> Possibly introduced only with a1854fae1414 ("rsi: improve RX - carnil> packet handling in USB interface") in 4.17-rc1. - bwh> I agree that commit a1854fae1414 introduced this. -Bugs: -upstream: released (5.3) [8b51dc7291473093c821195c4b6af85fadedbc2f] -4.19-upstream-stable: released (4.19.74) [3622d621e9beca76d53cd3007eb7b1d6e724716b] -4.9-upstream-stable: N/A "Vulnerability introduced later" -3.16-upstream-stable: N/A "Vulnerability introduced later" -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerability introduced later" -3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/active/CVE-2019-15505 b/active/CVE-2019-15505 deleted file mode 100644 index 96ed4cf0..00000000 --- a/active/CVE-2019-15505 +++ /dev/null @@ -1,16 +0,0 @@ -Description: media: technisat-usb2: break out of loop at end of buffer -References: - https://git.linuxtv.org/media_tree.git/commit/?id=0c4df39e504bf925ab666132ac3c98d6cbbe380b - https://lore.kernel.org/linux-media/20190821104408.w7krumcglxo6fz5q@gofer.mess.org/ - https://lore.kernel.org/lkml/b9b256cb-95f2-5fa1-9956-5a602a017c11@gmail.com/ -Notes: - bwh> Apparently introduced in 2.6.39 when technisat-usb2 driver was added. -Bugs: -upstream: released (5.4-rc1) [0c4df39e504bf925ab666132ac3c98d6cbbe380b] -4.19-upstream-stable: released (4.19.75) [b841a9f58d9c778d8c2c5f636dc06a53b9a47fa1] -4.9-upstream-stable: released (4.9.194) [994c6dcb4307759d440b8031e140d343b8611481] -3.16-upstream-stable: released (3.16.77) [2389a6543a1c2b3bd1ab5dae04d23c3ed9c95752] -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-15917 b/active/CVE-2019-15917 deleted file mode 100644 index 8db4a493..00000000 --- a/active/CVE-2019-15917 +++ /dev/null @@ -1,15 +0,0 @@ -Description: Bluetooth: hci_ldisc: Postpone HCI_UART_PROTO_READY bit set in hci_uart_set_proto() -References: -Notes: - bwh> Maybe introduced in 4.7 by commit 84cb3df02aea "Bluetooth: hci_ldisc: - bwh> Fix null pointer derefence in case of early data", but I suspect a - bwh> similar issue existed before that too. -Bugs: -upstream: released (5.1-rc1) [56897b217a1d0a91c9920cb418d6b3fe922f590a] -4.19-upstream-stable: released (4.19.32) [e365b94086f9dec02ddfcc193dcad72858c6d973] -4.9-upstream-stable: released (4.9.202) [3858f013de0ae5a19b8276944e12fd01b0cac979] -3.16-upstream-stable: released (3.16.74) [a79897227b81d588130813e83084b836733cb146] -sid: released (4.19.37-1) -4.19-buster-security: N/A "Fixed before branching point" -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.74-1) diff --git a/active/CVE-2019-15918 b/active/CVE-2019-15918 deleted file mode 100644 index 78e685c6..00000000 --- a/active/CVE-2019-15918 +++ /dev/null @@ -1,14 +0,0 @@ -Description: cifs: Fix lease buffer length error -References: -Notes: - bwh> Introduced in 4.14 by commit 9764c02fcbad "SMB3: Add support for - bwh> multidialect negotiate (SMB2.1 and later)". -Bugs: -upstream: released (5.1-rc6) [b57a55e2200ede754e4dc9cce4ba9402544b9365] -4.19-upstream-stable: released (4.19.73) [4061e662c8e9f5fb796b05fd2ab58fed8cd16d59] -4.9-upstream-stable: N/A "Vulnerability introduced later" -3.16-upstream-stable: N/A "Vulnerability introduced later" -sid: released (5.2.6-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerability introduced later" -3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/active/CVE-2019-16714 b/active/CVE-2019-16714 deleted file mode 100644 index aabd14e0..00000000 --- a/active/CVE-2019-16714 +++ /dev/null @@ -1,13 +0,0 @@ -Description: net/rds: Fix info leak in rds6_inc_info_copy() -References: -Notes: - bwh> Introduced by commit b7ff8b1036f0 "rds: Extend RDS API for IPv6 support" -Bugs: -upstream: released (5.3-rc7) [7d0a06586b2686ba80c4a2da5f91cb10ffbea736] -4.19-upstream-stable: released (4.19.72) [9484203d254d5e41f7120c15122b789f96647886] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-16746 b/active/CVE-2019-16746 deleted file mode 100644 index 9362db4a..00000000 --- a/active/CVE-2019-16746 +++ /dev/null @@ -1,13 +0,0 @@ -Description: nl80211: validate beacon head -References: - https://marc.info/?l=linux-wireless&m=156901391225058&w=2 -Notes: -Bugs: -upstream: released (5.4-rc2) [f88eb7c0d002a67ef31aeb7850b42ff69abc46dc] -4.19-upstream-stable: released (4.19.79) [1bd17a737c9e7e91483d9a603528b0e6d4c772f8] -4.9-upstream-stable: released (4.9.197) [a873afd7d888f7349bfabc9191afeb20eb1d3a45] -3.16-upstream-stable: released (3.16.79) [9eec2aca63328997846b52e91e88dab94ccd1414] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-17052 b/active/CVE-2019-17052 deleted file mode 100644 index 1a7b8117..00000000 --- a/active/CVE-2019-17052 +++ /dev/null @@ -1,12 +0,0 @@ -Description: ax25: enforce CAP_NET_RAW for raw sockets -References: -Notes: -Bugs: -upstream: released (5.4-rc1) [0614e2b73768b502fc32a75349823356d98aae2c] -4.19-upstream-stable: released (4.19.77) [6f0f18e532693ecc1e0c7938e0d63531ea62bc3e] -4.9-upstream-stable: released (4.9.195) [73b8d26c842a5a3be34a321beab1f97939d9794b] -3.16-upstream-stable: released (3.16.77) [2c675dab816278a1724c1e93b384c2f05a11cb31] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-17053 b/active/CVE-2019-17053 deleted file mode 100644 index 348c0b8e..00000000 --- a/active/CVE-2019-17053 +++ /dev/null @@ -1,12 +0,0 @@ -Description: ieee802154: enforce CAP_NET_RAW for raw sockets -References: -Notes: -Bugs: -upstream: released (5.4-rc1) [e69dbd4619e7674c1679cba49afd9dd9ac347eef] -4.19-upstream-stable: released (4.19.77) [dd651ab7a11436f787aed0a987c85864b261ff19] -4.9-upstream-stable: released (4.9.195) [ddca1f39c8980cb19db5ea6d51b8549288a7421b] -3.16-upstream-stable: released (3.16.77) [b8a15d59a9b26a734f6d8d5f10376f336f7d021b] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-17054 b/active/CVE-2019-17054 deleted file mode 100644 index 3360f5df..00000000 --- a/active/CVE-2019-17054 +++ /dev/null @@ -1,12 +0,0 @@ -Description: appletalk: enforce CAP_NET_RAW for raw sockets -References: -Notes: -Bugs: -upstream: released (5.4-rc1) [6cc03e8aa36c51f3b26a0d21a3c4ce2809c842ac] -4.19-upstream-stable: released (4.19.77) [6fbf866276089853727dd9b31f1d251e61dde367] -4.9-upstream-stable: released (4.9.195) [08d2af9358c1937acf97417dba9a03a40149c4d2] -3.16-upstream-stable: released (3.16.77) [2d4020439bd19f2a498a7fccd8755521a90b2886] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-17055 b/active/CVE-2019-17055 deleted file mode 100644 index b6120cf3..00000000 --- a/active/CVE-2019-17055 +++ /dev/null @@ -1,12 +0,0 @@ -Description: mISDN: enforce CAP_NET_RAW for raw sockets -References: -Notes: -Bugs: -upstream: released (5.4-rc1) [b91ee4aa2a2199ba4d4650706c272985a5a32d80] -4.19-upstream-stable: released (4.19.77) [50dddec689cb2105f6bccf4a2c6fe43dcc3295d7] -4.9-upstream-stable: released (4.9.195) [bb439ee217acbf7835af634f08875540c514632f] -3.16-upstream-stable: released (3.16.77) [f49bd6510620b9cd434b87bea639f07dfde56f09] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-17056 b/active/CVE-2019-17056 deleted file mode 100644 index fb010058..00000000 --- a/active/CVE-2019-17056 +++ /dev/null @@ -1,12 +0,0 @@ -Description: nfc: enforce CAP_NET_RAW for raw sockets -References: -Notes: -Bugs: -upstream: released (5.4-rc1) [3a359798b176183ef09efb7a3dc59abad1cc7104] -4.19-upstream-stable: released (4.19.77) [33fe1f517e29566d842535038be227c71a4bd54d] -4.9-upstream-stable: released (4.9.195) [45a9e9bc5d6742988df799dafbf26dca8e0dada3] -3.16-upstream-stable: released (3.16.77) [bc3d2e9cfdc5c1b7e5ed34eb5279e47d462b4d5c] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-17075 b/active/CVE-2019-17075 deleted file mode 100644 index 54044d80..00000000 --- a/active/CVE-2019-17075 +++ /dev/null @@ -1,15 +0,0 @@ -Description: cxgb4: do not dma memory off of the stack -References: - https://lore.kernel.org/lkml/20191001165611.GA3542072@kroah.com/ -Notes: - bwh> I believe this "worked" on Debian supported architectures until 4.9 - bwh> introduced vmapped stacks for amd64. -Bugs: -upstream: released (5.4-rc3) [3840c5b78803b2b6cc1ff820100a74a092c40cbb] -4.19-upstream-stable: released (4.19.81) [27414f90ff6e1d7f6657e4a820b04a7b2d760272] -4.9-upstream-stable: released (4.9.198) [84f5b67df81a9f333afa81855f6fa3fdcd954463] -3.16-upstream-stable: ignored "Not a problem in practice" -sid: released (5.3.7-1) [bugfix/all/RDMA-cxgb4-Do-not-dma-memory-off-of-the-stack.patch] -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: ignored "Not a problem in practice" diff --git a/active/CVE-2019-17133 b/active/CVE-2019-17133 deleted file mode 100644 index 9c861cac..00000000 --- a/active/CVE-2019-17133 +++ /dev/null @@ -1,14 +0,0 @@ -Description: cfg80211: wext: avoid copying malformed SSIDs -References: - https://marc.info/?l=linux-wireless&m=157018270915487&w=2 -Notes: - carnil> In 5.3.x fixed in 5.3.8. -Bugs: -upstream: released (5.4-rc4) [4ac2813cc867ae563a1ba5a9414bfb554e5796fa] -4.19-upstream-stable: released (4.19.81) [73c066a9552a6d33ed7de002855337d1c966e8ce] -4.9-upstream-stable: released (4.9.198) [49d84740f8a7040354ef93bf5915a4b3e651e71b] -3.16-upstream-stable: released (3.16.77) [e70efb76ea2eb9f08dc627d93d35a8e5c065346d] -sid: released (5.3.9-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-17666 b/active/CVE-2019-17666 deleted file mode 100644 index c1352311..00000000 --- a/active/CVE-2019-17666 +++ /dev/null @@ -1,13 +0,0 @@ -Description: rtlwifi: Fix potential overflow on P2P code -References: - https://lkml.org/lkml/2019/10/16/1226 -Notes: -Bugs: -upstream: released (5.4-rc6) [8c55dedb795be8ec0cf488f98c03a1c2176f7fb1] -4.19-upstream-stable: released (4.19.82) [64efcbc7a5a3c7a14e42ccf7b8a7e7667d672a33] -4.9-upstream-stable: released (4.9.199) [4a2fbab9e82fb662ad3419525742a1ddfc29a7b9] -3.16-upstream-stable: released (3.16.77) [b78c8469ceff4288d1092e22bfb277d3bd0d7147] -sid: released (5.3.9-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-18282 b/active/CVE-2019-18282 deleted file mode 100644 index caddd29c..00000000 --- a/active/CVE-2019-18282 +++ /dev/null @@ -1,15 +0,0 @@ -Description: net/flow_dissector: switch to siphash -References: -Notes: - bwh> The issue is not in flow dissector itself, but in the use of flow - bwh> dissector's hashing to generate flow labels. This was introduced - bwh> as an option in 3.17 and enabled by default in 4.3. -Bugs: -upstream: released (5.4-rc6) [55667441c84fa5e0911a0aac44fb059c15ba6da2] -4.19-upstream-stable: released (4.19.83) [558d2bdad5f6a0dd65ed7ed4f74419e826a97759] -4.9-upstream-stable: released (4.9.200) [1f94465d13ace2d4610c4eb2b362454ce2a9d87c] -3.16-upstream-stable: N/A "Vulnerability introduced later" -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/active/CVE-2019-18660 b/active/CVE-2019-18660 deleted file mode 100644 index c3a34051..00000000 --- a/active/CVE-2019-18660 +++ /dev/null @@ -1,17 +0,0 @@ -Description: powerpc: missing Spectre-RSB mitigation -References: - https://www.openwall.com/lists/oss-security/2019/11/27/1 -Notes: - carnil> Technically (resp. from CVE assignment point of view) the CVE - carnil> is solely for the missing Spectre-RSB mitigation and - carnil> 39e72bf96f58 ("powerpc/book3s64: Fix link stack flush on - carnil> context switch"). -Bugs: -upstream: released (5.5-rc1) [39e72bf96f5847ba87cc5bd7a3ce0fed813dc9ad, af2e8c68b9c5403f77096969c516f742f5bb29e0] -4.19-upstream-stable: released (4.19.87) [0a60d4bddc0ba6a7e06d10efa59f7861837860b0, 345712c95eec44bf414782b33e6d5a550fe62b3b] -4.9-upstream-stable: released (4.9.204) [113408cdaec11a6e34d4edabb134a335dd4896b3, e2c87b1ba04bd5042f6db0780ed55abaf4836378] -3.16-upstream-stable: ignored "No speculation mitigations available for powerpc" -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: ignored "powerpc not supported in LTS" diff --git a/active/CVE-2019-18683 b/active/CVE-2019-18683 deleted file mode 100644 index 108dda85..00000000 --- a/active/CVE-2019-18683 +++ /dev/null @@ -1,15 +0,0 @@ -Description: media: vivid: Fix wrong locking that causes race conditions on streaming stop -References: - https://www.openwall.com/lists/oss-security/2019/11/02/1 - https://lore.kernel.org/lkml/20191102190327.24903-1-alex.popov@linux.com/ - https://lore.kernel.org/lkml/20191103221719.27118-1-alex.popov@linux.com/ -Notes: -Bugs: -upstream: released (5.5-rc1) [6dcd5d7a7a29c1e4b8016a06aed78cd650cd8c27] -4.19-upstream-stable: released (4.19.87) [467052f6ea5a51524992e43f02b543550495c391] -4.9-upstream-stable: released (4.9.204) [012a42dbc770d3e815cae536917245d74621c552] -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-18786 b/active/CVE-2019-18786 deleted file mode 100644 index 29baeb75..00000000 --- a/active/CVE-2019-18786 +++ /dev/null @@ -1,15 +0,0 @@ -Description: media: rcar_drif: fix a memory disclosure -References: - https://patchwork.linuxtv.org/patch/59542/ -Notes: - bwh> Introduced in 4.13 by commit 7625ee981af1 "[media] media: platform: - bwh> rcar_drif: Add DRIF support". -Bugs: -upstream: released (5.5-rc1) [d39083234c60519724c6ed59509a2129fd2aed41] -4.19-upstream-stable: released (4.19.92) [debdd16cbd99ffc767227685e2738e5b495b7c54] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.4.8-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-18806 b/active/CVE-2019-18806 deleted file mode 100644 index 543a66de..00000000 --- a/active/CVE-2019-18806 +++ /dev/null @@ -1,16 +0,0 @@ -Description: net: qlogic: Fix memory leak in ql_alloc_large_buffers -References: -Notes: - bwh> I think this is an invalid issue and an incorrect fix; see - bwh> https://lore.kernel.org/stable/71577c0106fb9bcc28cff3f507e73bf2d3cb3713.camel@decadent.org.uk/ - bwh> and - bwh> https://lore.kernel.org/netdev/20191217015740.GA31381@decadent.org.uk/T/ -Bugs: -upstream: released (5.4-rc2) [1acb8f2a7a9f10543868ddd737e37424d5c36cf4] -4.19-upstream-stable: released (4.19.78) [9d0995cc268b4a431dbfb29db5cac36546732bc0] -4.9-upstream-stable: released (4.9.196) [3ae6d4c9473378d57bcad5a6e102c8ba42efd014] -3.16-upstream-stable: released (3.16.81) [e1db96134ab329054b73c4075949053e43ac7208] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: ignored "Invalid issue" diff --git a/active/CVE-2019-18809 b/active/CVE-2019-18809 deleted file mode 100644 index c7168ce4..00000000 --- a/active/CVE-2019-18809 +++ /dev/null @@ -1,17 +0,0 @@ -Description: media: usb: fix memory leak in af9005_identify_state -References: - https://github.com/torvalds/linux/commit/2289adbfa559050d2a38bcd9caac1c18b800e928 -Notes: - carnil> Fix not yet in Linus' tree. - bwh> Introduced in 4.9 by commit c58b84ee467b "[media] af9005: don't do DMA - bwh> on stack". Doesn't seem to have any security impact. - carnil> Fixed as well in 5.4.9. -Bugs: -upstream: released (5.5-rc1) [2289adbfa559050d2a38bcd9caac1c18b800e928] -4.19-upstream-stable: released (4.19.94) [d933de8115f3263fd50cf3b1f1dac2faff02fd89] -4.9-upstream-stable: released (4.9.209) [129139a26325d2274a226407d1e7b6f1eb40b456] -3.16-upstream-stable: N/A "Bug introduced later" -sid: released (5.4.13-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Bug introduced later" diff --git a/active/CVE-2019-18813 b/active/CVE-2019-18813 deleted file mode 100644 index 8b9958ff..00000000 --- a/active/CVE-2019-18813 +++ /dev/null @@ -1,15 +0,0 @@ -Description: usb: dwc3: pci: prevent memory leak in dwc3_pci_probe -References: -Notes: - bwh> Intrdocued in 4.19 by commit 1a7b12f69a94 "usb: dwc3: pci: Supply - bwh> device properties via driver data". No security impact since this - bwh> is on the probe path. Also not enabled in any Debian config. -Bugs: -upstream: released (5.4-rc6) [9bbfceea12a8f145097a27d7c7267af25893c060] -4.19-upstream-stable: released (4.19.84) [10eb9abd21bad2a9726f50557b38924cb8d81ccd] -4.9-upstream-stable: N/A "Bug introduced later" -3.16-upstream-stable: N/A "Bug introduced later" -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Bug introduced later" -3.16-jessie-security: N/A "Bug introduced later" diff --git a/active/CVE-2019-19037 b/active/CVE-2019-19037 deleted file mode 100644 index 5bd5a171..00000000 --- a/active/CVE-2019-19037 +++ /dev/null @@ -1,18 +0,0 @@ -Description: ext4: Fix ext4_empty_dir() for directories with holes -References: - https://github.com/bobfuzzer/CVE/tree/master/CVE-2019-19037 - https://lore.kernel.org/stable/20191202170213.4761-2-jack@suse.cz/ -Notes: - carnil> commit fixes Fixes: 4e19d6b65fb4 ("ext4: allow directory - carnil> holes") which is in 5.3-rc1 but was backported to various other - carnil> stable trees in 5.2.4, 5.1.21, 4.19.62, 4.14.135 and 4.9.187 - carnil> already. -Bugs: -upstream: released (5.5-rc3) [64d4ce892383b2ad6d782e080d25502f91bf2a38] -4.19-upstream-stable: released (4.19.92) [1e62ac6b1307129c0f9ca68e9db4227239b4ab19] -4.9-upstream-stable: released (4.9.208) [dfcbd407f81e645601bccef8912af79b3d1ca87b] -3.16-upstream-stable: N/A "Vulnerability introduced later" -sid: released (5.4.8-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/active/CVE-2019-19045 b/active/CVE-2019-19045 deleted file mode 100644 index b7a4185f..00000000 --- a/active/CVE-2019-19045 +++ /dev/null @@ -1,13 +0,0 @@ -Description: net/mlx5: prevent memory leak in mlx5_fpga_conn_create_cq -References: -Notes: - bwh> Introduced in 4.13 by commit 537a50574175. -Bugs: -upstream: released (5.4-rc6) [c8c2a057fdc7de1cd16f4baa51425b932a42eb39] -4.19-upstream-stable: released (4.19.84) [42de3a902443b64c6e3cf9c61d9cd6f30b2c0d67] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19048 b/active/CVE-2019-19048 deleted file mode 100644 index 000ccced..00000000 --- a/active/CVE-2019-19048 +++ /dev/null @@ -1,14 +0,0 @@ -Description: virt: vbox: fix memory leak in hgcm_call_preprocess_linaddr -References: -Notes: - bwh> Introduced in 4.16 by commit 579db9d45cb4 "virt: Add vboxguest VMMDEV - bwh> communication code". -Bugs: -upstream: released (5.4-rc3) [e0b0cb9388642c104838fac100a4af32745621e2] -4.19-upstream-stable: released (4.19.82) [c2ea451f22f180e9e46225f54b5ec50c50bb639f] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.9-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19052 b/active/CVE-2019-19052 deleted file mode 100644 index 1bca474c..00000000 --- a/active/CVE-2019-19052 +++ /dev/null @@ -1,14 +0,0 @@ -Description: can: gs_usb: gs_can_open(): prevent memory leak -References: -Notes: - bwh> Introduced in 3.16 by commit d08e973a77d1 "can: gs_usb: Added support - bwh> for the GS_USB CAN devices". -Bugs: -upstream: released (5.4-rc7) [fb5be6a7b4863ecc44963bb80ca614584b6c7817] -4.19-upstream-stable: released (4.19.84) [9289226f69822de0b716c0fbfc31db0283f14e2b] -4.9-upstream-stable: released (4.9.201) [b46a2067f36d7c5f2f259c4ed476359e6e9d668f] -3.16-upstream-stable: released (3.16.79) [f26d980434a06f44b693a26a87aa5300fa4016fd] -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19056 b/active/CVE-2019-19056 deleted file mode 100644 index 2363c7ed..00000000 --- a/active/CVE-2019-19056 +++ /dev/null @@ -1,15 +0,0 @@ -Description: mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf -References: - https://github.com/torvalds/linux/commit/db8fd2cde93227e566a412cf53173ffa227998bc -Notes: - bwh> Introduced in 3.9 by commit fc3314609047 "mwifiex: use pci_alloc/ - bwh> free_consistent APIs for PCIe". -Bugs: -upstream: released (5.5-rc1) [db8fd2cde93227e566a412cf53173ffa227998bc] -4.19-upstream-stable: released (4.19.96) [f2bde0e9989e243345316e3c96b352ab94037340] -4.9-upstream-stable: released (4.9.210) [9bba4330671eaf1d21ac6025f950e7cca92f7aca] -3.16-upstream-stable: released (3.16.79) [f0eed3b1a34f1e7d8b2c06ad5ddf0ea60aea71ca] -sid: released (5.4.13-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19057 b/active/CVE-2019-19057 deleted file mode 100644 index 19ce341f..00000000 --- a/active/CVE-2019-19057 +++ /dev/null @@ -1,15 +0,0 @@ -Description: mwifiex: pcie: Fix memory leak in mwifiex_pcie_init_evt_ring -References: - https://github.com/torvalds/linux/commit/d10dcb615c8e29d403a24d35f8310a7a53e3050c -Notes: - bwh> Introduced in 3.9 by commit fc3314609047 "mwifiex: use pci_alloc/ - bwh> free_consistent APIs for PCIe". -Bugs: -upstream: released (5.5-rc1) [d10dcb615c8e29d403a24d35f8310a7a53e3050c] -4.19-upstream-stable: released (4.19.92) [1b3e52db38471d5ac896eb9be111565e3734d5b5] -4.9-upstream-stable: released (4.9.208) [716156b896197824e55fc2f8244c8c43e0ed73e1] -3.16-upstream-stable: released (3.16.79) [914927c7bac4ecd2351bdee0cd5b2b1c11150342] -sid: released (5.4.8-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19058 b/active/CVE-2019-19058 deleted file mode 100644 index 4462f0ae..00000000 --- a/active/CVE-2019-19058 +++ /dev/null @@ -1,14 +0,0 @@ -Description: iwlwifi: dbg_ini: fix memory leak in alloc_sgtable -References: -Notes: - carnil> Introduced in 7e62a699aafb ("iwlwifi: mvm: use - carnil> dev_coredumpsg()") in 4.10-rc1. -Bugs: -upstream: released (5.4-rc4) [b4b814fec1a5a849383f7b3886b654a13abbda7d] -4.19-upstream-stable: released (4.19.97) [09044a4a142404799e519def0bbfcc98fa68c677] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.4.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19059 b/active/CVE-2019-19059 deleted file mode 100644 index 7b002be4..00000000 --- a/active/CVE-2019-19059 +++ /dev/null @@ -1,14 +0,0 @@ -Description: iwlwifi: pcie: fix memory leaks in iwl_pcie_ctxt_info_gen3_init -References: -Notes: - carnil> Fixes 2ee824026288 ("iwlwifi: pcie: support context information - carnil> for 22560 devices") in 4.19-rc1. -Bugs: -upstream: released (5.4-rc4) [0f4f199443faca715523b0659aa536251d8b978f] -4.19-upstream-stable: released (4.19.97) [6e41dd9731e13b0bdf2f57f84b9d25d009bd9f87] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.4.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19062 b/active/CVE-2019-19062 deleted file mode 100644 index c783a598..00000000 --- a/active/CVE-2019-19062 +++ /dev/null @@ -1,16 +0,0 @@ -Description: crypto: user - fix memory leak in crypto_report -References: - https://github.com/torvalds/linux/commit/ffdde5932042600c6807d46c1550b28b0db6a3bc -Notes: - bwh> Introduced in 3.2 by commit a38f7907b926 "crypto: Add userspace - bwh> configuration API". - carnil> Fixed as well in 5.3.16 and 5.4.3. -Bugs: -upstream: released (5.5-rc1) [ffdde5932042600c6807d46c1550b28b0db6a3bc] -4.19-upstream-stable: released (4.19.89) [351a567ebf2482de4dd5e5bbd539f2175540b717] -4.9-upstream-stable: released (4.9.207) [f427e1fcf77416ed14a716416c0faf2f02a1e68b] -3.16-upstream-stable: released (3.16.79) [52373b487ee420c43e1d9d01b4b8c11bb6e9bdbf] -sid: released (5.4.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19065 b/active/CVE-2019-19065 deleted file mode 100644 index 39a24ef0..00000000 --- a/active/CVE-2019-19065 +++ /dev/null @@ -1,14 +0,0 @@ -Description: RDMA/hfi1: Prevent memory leak in sdma_init -References: -Notes: - bwh> Intrdocued in 4.12 by commit 5a52a7acf7e2 "IB/hfi1: NULL pointer - bwh> dereference when freeing rhashtable". -Bugs: -upstream: released (5.4-rc3) [34b3be18a04ecdc610aae4c48e5d1b799d8689f6] -4.19-upstream-stable: released (4.19.82) [962cff4f3f89acf54b6fb418e7ff386b720b0fd6] -4.9-upstream-stable: N/A "Vulnerability introduced later" -3.16-upstream-stable: N/A "Vulnerability introduced later" -sid: released (5.3.9-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerability introduced later" -3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/active/CVE-2019-19066 b/active/CVE-2019-19066 deleted file mode 100644 index 15223dab..00000000 --- a/active/CVE-2019-19066 +++ /dev/null @@ -1,14 +0,0 @@ -Description: scsi: bfa: release allocated memory in case of error -References: - https://github.com/torvalds/linux/commit/0e62395da2bd5166d7c9e14cbc7503b256a34cb0 -Notes: - bwh> Introduced in 2.6.37 by commit a36c61f9025b "[SCSI] bfa: cleanup driver". -Bugs: -upstream: released (5.5-rc1) [0e62395da2bd5166d7c9e14cbc7503b256a34cb0] -4.19-upstream-stable: released (4.19.96) [486f51201528126bec2c647fa9d4216fc4fda91b] -4.9-upstream-stable: released (4.9.210) [78cb846f4aea6e20fc942d7bb8930107d1c6e34f] -3.16-upstream-stable: released (3.16.79) [0669f62b66de87c6628edc6b5e7e7b317a4b8876] -sid: released (5.4.13-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19068 b/active/CVE-2019-19068 deleted file mode 100644 index 3414d425..00000000 --- a/active/CVE-2019-19068 +++ /dev/null @@ -1,15 +0,0 @@ -Description: rtl8xxxu: prevent leaking urb -References: - https://github.com/torvalds/linux/commit/a2cdd07488e666aa93a49a3fc9c9b1299e27ef3c -Notes: - bwh> Introduced in 4.4 by commit 26f1fad29ad9 "New driver: rtl8xxxu - bwh> (mac80211)". -Bugs: -upstream: released (5.5-rc1) [a2cdd07488e666aa93a49a3fc9c9b1299e27ef3c] -4.19-upstream-stable: released (4.19.96) [0e27512c5d0bc2c3d33c1e7f73a8983015c82b83] -4.9-upstream-stable: released (4.9.210) [2c00bebd0b959fe8bec6d4a1a07010394b8008e4] -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.4.13-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19071 b/active/CVE-2019-19071 deleted file mode 100644 index 5d30f172..00000000 --- a/active/CVE-2019-19071 +++ /dev/null @@ -1,16 +0,0 @@ -Description: rsi: release skb if rsi_prepare_beacon fails -References: - https://github.com/torvalds/linux/commit/d563131ef23cbc756026f839a82598c8445bc45f -Notes: - bwh> Introduced in 4.14 by commit d26a9559403c "rsi: add beacon changes for - bwh> AP mode". - carnil> Fixed as well in 5.3.16 and 5.4.3 already. -Bugs: -upstream: released (5.5-rc1) [d563131ef23cbc756026f839a82598c8445bc45f] -4.19-upstream-stable: released (4.19.89) [5da96cc31633a9076404621ebb89bbe78f2c8676] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.4.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19077 b/active/CVE-2019-19077 deleted file mode 100644 index b07d9467..00000000 --- a/active/CVE-2019-19077 +++ /dev/null @@ -1,14 +0,0 @@ -Description: RDMA: Fix goto target to release the allocated memory -References: -Notes: - carnil> Introduced in 37cb11acf1f7 ("RDMA/bnxt_re: Add SRQ support for - carnil> Broadcom adapters") in 4.16-rc1. -Bugs: -upstream: released (5.4-rc1) [4a9d46a9fe14401f21df69cea97c62396d5fb053] -4.19-upstream-stable: released (4.19.97) [d203ff6a3059b7fc3a9b48048eaf5641ed7fda2c] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.4.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19078 b/active/CVE-2019-19078 deleted file mode 100644 index 5bfb4f39..00000000 --- a/active/CVE-2019-19078 +++ /dev/null @@ -1,15 +0,0 @@ -Description: ath10k: fix memory leak -References: - https://github.com/torvalds/linux/commit/b8d17e7d93d2beb89e4f34c59996376b8b544792 -Notes: - bwh> Introduced in 4.14 by commit 4db66499df91 "ath10k: add initial USB - bwh> support". -Bugs: -upstream: released (5.5-rc1) [b8d17e7d93d2beb89e4f34c59996376b8b544792] -4.19-upstream-stable: released (4.19.96) [aed1b68eadf22513ac1fbd389f591f91c8bdaaf5] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.4.13-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19079 b/active/CVE-2019-19079 deleted file mode 100644 index cecc7ecc..00000000 --- a/active/CVE-2019-19079 +++ /dev/null @@ -1,14 +0,0 @@ -Description: net: qrtr: fix memort leak in qrtr_tun_write_iter -References: -Notes: - bwh> Introduced in 4.18 by commit 28fb4e59a47d "net: qrtr: Expose tunneling - bwh> endpoint to user space". Driver is not enabled in any Debian config. -Bugs: -upstream: released (5.3) [a21b7f0cff1906a93a0130b74713b15a0b36481d] -4.19-upstream-stable: released (4.19.89) [754e3c0c31c96cf3a4a54ed2a8c63cca28109136] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19080 b/active/CVE-2019-19080 deleted file mode 100644 index d998eff5..00000000 --- a/active/CVE-2019-19080 +++ /dev/null @@ -1,14 +0,0 @@ -Description: nfp: flower: prevent memory leak in nfp_flower_spawn_phy_reprs -References: -Notes: - bwh> Introduced in 4.18 by commit b94524529741 "nfp: flower: add per repr - bwh> private data for LAG offload". -Bugs: -upstream: released (5.4-rc1) [8572cea1461a006bce1d06c0c4b0575869125fa4] -4.19-upstream-stable: released (4.19.77) [5b6c791f494d5e770dfd015390386f321b9a94da] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19081 b/active/CVE-2019-19081 deleted file mode 100644 index c373879c..00000000 --- a/active/CVE-2019-19081 +++ /dev/null @@ -1,14 +0,0 @@ -Description: nfp: flower: fix memory leak in nfp_flower_spawn_vnic_reprs -References: -Notes: - bwh> Introduced in 4.18 by commit b94524529741 "nfp: flower: add per repr - bwh> private data for LAG offload". -Bugs: -upstream: released (5.4-rc1) [8ce39eb5a67aee25d9f05b40b673c95b23502e3e] -4.19-upstream-stable: released (4.19.79) [04e0c84f137dd07aa931c00db1a2ac80f3be4be5] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19227 b/active/CVE-2019-19227 deleted file mode 100644 index f1234be3..00000000 --- a/active/CVE-2019-19227 +++ /dev/null @@ -1,12 +0,0 @@ -Description: appletalk: Fix potential NULL pointer dereference in unregister_snap_clien -References: -Notes: -Bugs: -upstream: released (5.1-rc3) [9804501fa1228048857910a6bf23e085aade37cc] -4.19-upstream-stable: released (4.19.89) [0977763a13fd87a7aebe376dc96385758de3aa9e] -4.9-upstream-stable: released (4.9.207) [540b341012ba9b8e2963be3241cea229d4e4804d] -3.16-upstream-stable: released (3.16.79) [1551894964c90588b285d3a4f7da516e0ee9025a] -sid: released (5.2.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19332 b/active/CVE-2019-19332 deleted file mode 100644 index f8473af2..00000000 --- a/active/CVE-2019-19332 +++ /dev/null @@ -1,15 +0,0 @@ -Description: KVM: x86: fix out-of-bounds write in KVM_GET_EMULATED_CPUID -References: - https://lore.kernel.org/kvm/000000000000ea5ec20598d90e50@google.com/ - https://www.openwall.com/lists/oss-security/2019/12/16/1 -Notes: - carnil> Fixed as well in 5.4.3 and 5.3.16 already. -Bugs: -upstream: released (5.5-rc1) [433f4ba1904100da65a311033f17a9bf586b287e] -4.19-upstream-stable: released (4.19.89) [5119ffd480b644d8bc9af741cc8ef435a7ec5ff7] -4.9-upstream-stable: released (4.9.207) [8b587e3f1424fae01f9c7e78d8d294bcb71f6f41] -3.16-upstream-stable: released (3.16.79) [21377f88c2757c6ee3e28407fb1c44b4bdf7e6b2] -sid: released (5.4.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19523 b/active/CVE-2019-19523 deleted file mode 100644 index 5426e822..00000000 --- a/active/CVE-2019-19523 +++ /dev/null @@ -1,13 +0,0 @@ -Description: USB: adutux: fix use-after-free on disconnect -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.4-rc3) [44efc269db7929f6275a1fa927ef082e533ecde0] -4.19-upstream-stable: released (4.19.80) [316f51d7759735a5295301ab22a7c6231b49c24f] -4.9-upstream-stable: released (4.9.197) [aa1b499d5f706c67a0acbe184e0ec32e8c47489b] -3.16-upstream-stable: released (3.16.79) [22cbb8fb12b3b5101260915162ad2b0b56a9284d] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19524 b/active/CVE-2019-19524 deleted file mode 100644 index 8a01253f..00000000 --- a/active/CVE-2019-19524 +++ /dev/null @@ -1,13 +0,0 @@ -Description: Input: ff-memless - kill timer in destroy() -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.4-rc8) [fa3a5a1880c91bb92594ad42dfe9eedad7996b86] -4.19-upstream-stable: released (4.19.85) [c02230815282a436366d3d0d6de6d2636dd71b74] -4.9-upstream-stable: released (4.9.203) [1ce4561d12a08be9de2f2ef8ace700e55fc4835c] -3.16-upstream-stable: released (3.16.79) [8145f2181955c7c95f42a7f71b81ff91bc9e7b8c] -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19525 b/active/CVE-2019-19525 deleted file mode 100644 index 8c1b5e18..00000000 --- a/active/CVE-2019-19525 +++ /dev/null @@ -1,13 +0,0 @@ -Description: ieee802154: atusb: fix use-after-free at disconnect -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.4-rc2) [7fd25e6fc035f4b04b75bca6d7e8daa069603a76] -4.19-upstream-stable: released (4.19.79) [3f41e88f4bd44284c575ad3fb579581a16b39069] -4.9-upstream-stable: released (4.9.197) [2f2f3ffa761793f2db2f3b0bc6476a069061cb9c] -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19526 b/active/CVE-2019-19526 deleted file mode 100644 index c2c077a3..00000000 --- a/active/CVE-2019-19526 +++ /dev/null @@ -1,15 +0,0 @@ -Description: NFC: pn533: fix use-after-free and memleaks -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: - bwh> Introduced in 4.12 by commit 32ecc75ded72 ("NFC: pn533: change order - bwh> operations in dev registation". -Bugs: -upstream: released (5.4-rc4) [6af3aa57a0984e061f61308fe181a9a12359fecc] -4.19-upstream-stable: released (4.19.82) [24aaf7f4528f0df0f29667d3921f4a63aa7b806c] -4.9-upstream-stable: N/A "Vulnerability introduced later" -3.16-upstream-stable: N/A "Vulnerability introduced later" -sid: released (5.3.9-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerability introduced later" -3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/active/CVE-2019-19527 b/active/CVE-2019-19527 deleted file mode 100644 index ba8c6f11..00000000 --- a/active/CVE-2019-19527 +++ /dev/null @@ -1,14 +0,0 @@ -Description: Use-after-free bug in drivers/hid/usbhid/hiddev.c driver -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: - carnil> Please double-check this triage/assessment. -Bugs: -upstream: released (5.3-rc4) [6d4472d7bec39917b54e4e80245784ea5d60ce49, 9c09b214f30e3c11f9b0b03f89442df03643794d] -4.19-upstream-stable: released (4.19.68) [b545dc9debe69ca513b93f4a244451e9be14b0c5, 0aab1a4653a6a21509e8add4bb460be76fcf9c70] -4.9-upstream-stable: released (4.9.190) [963a14fb9c43f0a6b38fbe3da0b894a147c71388, 52aaeae5f22247659238a06c36973775f57189f3] -3.16-upstream-stable: released (3.16.79) [a2133df2ca08f0d320e651f682f66a1097e6b752, daec20c79bdc41b44b651aa8c9506cb138a83952] -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19528 b/active/CVE-2019-19528 deleted file mode 100644 index 393d582d..00000000 --- a/active/CVE-2019-19528 +++ /dev/null @@ -1,16 +0,0 @@ -Description: USB: iowarrior: fix use-after-free on disconnect -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: - carnil> The fix c468a8aa790e ("usb: iowarrior: fix deadlock on - carnil> disconnect") in 5.3-rc4 (and backported to 5.2.9, 4.19.67 and - carnil> 4.9.190) introduced the issue. -Bugs: -upstream: released (5.4-rc3) [edc4746f253d907d048de680a621e121517f484b] -4.19-upstream-stable: released (4.19.80) [2fdcf7e19bdefc683da824264c0898af39bf8d50] -4.9-upstream-stable: released (4.9.197) [323f425a7618fdb0b961dec2c58685fa32eafa1b] -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code not yet present in released version" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19529 b/active/CVE-2019-19529 deleted file mode 100644 index 8f9b9ba7..00000000 --- a/active/CVE-2019-19529 +++ /dev/null @@ -1,15 +0,0 @@ -Description: can: mcba_usb: fix use-after-free on disconnect -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: - bwh> Introduced in 4.12 by commit 51f3baad7de9 "can: mcba_usb: Add support - bwh> for Microchip CAN BUS Analyzer". -Bugs: -upstream: released (5.4-rc7) [4d6636498c41891d0482a914dd570343a838ad79] -4.19-upstream-stable: released (4.19.84) [ce9b94da0e043b7b0ec1bd3d0e451d956acff9c1] -4.9-upstream-stable: N/A "Vulnerable code not present" -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerable code not present" -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19530 b/active/CVE-2019-19530 deleted file mode 100644 index 3ca3c9c9..00000000 --- a/active/CVE-2019-19530 +++ /dev/null @@ -1,13 +0,0 @@ -Description: usb: cdc-acm: make sure a refcount is taken early enough -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.3-rc5) [c52873e5a1ef72f845526d9f6a50704433f9c625] -4.19-upstream-stable: released (4.19.68) [c02c0249ce5523a7a264136ed36f857b85555bac] -4.9-upstream-stable: released (4.9.190) [fccd6134d5addf2be1407e3250efdc854b5c5d8a] -3.16-upstream-stable: released (3.16.78) [3a8f54a68c9868ddae64603f2ddee082c1737075] -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19531 b/active/CVE-2019-19531 deleted file mode 100644 index 769c5491..00000000 --- a/active/CVE-2019-19531 +++ /dev/null @@ -1,13 +0,0 @@ -Description: usb: yurex: Fix use-after-free in yurex_delete -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.3-rc4) [fc05481b2fcabaaeccf63e32ac1baab54e5b6963] -4.19-upstream-stable: released (4.19.67) [33f2240acfa8b4017ee5dd64601c8a5ec7f53b4e] -4.9-upstream-stable: released (4.9.190) [e253114f73134cf6f29b453176fb537441e12371] -3.16-upstream-stable: released (3.16.78) [8f6204f2adba5354b65bd0f37b8d930e49df6420] -sid: released (5.2.9-1) -4.19-buster-security: released (4.19.67-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19532 b/active/CVE-2019-19532 deleted file mode 100644 index 0ec2009b..00000000 --- a/active/CVE-2019-19532 +++ /dev/null @@ -1,13 +0,0 @@ -Description: HID: Fix assumption that devices have inputs -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.4-rc6) [d9d4b1e46d9543a82c23f6df03f4ad697dab361b] -4.19-upstream-stable: released (4.19.82) [8a01c4b908cf0a5367d3309c1c0d4e9be655ce00] -4.9-upstream-stable: released (4.9.199) [7b5e3ad5d582e252d971ee599a3f63f30b70ccb1] -3.16-upstream-stable: released (3.16.79) [f703c175f8e428959a33cdadb3e09986f14390ce] -sid: released (5.3.9-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19533 b/active/CVE-2019-19533 deleted file mode 100644 index db5e9320..00000000 --- a/active/CVE-2019-19533 +++ /dev/null @@ -1,13 +0,0 @@ -Description: media: ttusb-dec: Fix info-leak in ttusb_dec_send_command() -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.4-rc1) [a10feaf8c464c3f9cfdd3a8a7ce17e1c0d498da1] -4.19-upstream-stable: released (4.19.77) [8630a4d13683095fbf14091d59a20e1ac71fdd6b] -4.9-upstream-stable: released (4.9.195) [70d5b96a1ed385a0ef520a44a18fbf6d795f1b84] -3.16-upstream-stable: released (3.16.79) [89577bea6adf8cd2a1b97c91f7266bb56aa181b0] -sid: released (5.3.7-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19534 b/active/CVE-2019-19534 deleted file mode 100644 index ff7da283..00000000 --- a/active/CVE-2019-19534 +++ /dev/null @@ -1,13 +0,0 @@ -Description: can: peak_usb: fix slab info leak -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.4-rc7) [f7a1337f0d29b98733c8824e165fca3371d7d4fd] -4.19-upstream-stable: released (4.19.84) [a7be2debb769092c7c07b9a866b055d8bee5afaf] -4.9-upstream-stable: released (4.9.201) [da281558d20bfbf82823cab457ba7d343ba6b0a0] -3.16-upstream-stable: released (3.16.79) [f13615187cd8069c0f1c492e8f244a0c69d0663e] -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19535 b/active/CVE-2019-19535 deleted file mode 100644 index b1234f8f..00000000 --- a/active/CVE-2019-19535 +++ /dev/null @@ -1,15 +0,0 @@ -Description: can: peak_usb: pcan_usb_fd: Fix info-leaks to USB devices -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: - bwh> Introduced in 4.0 by commit 0a25e1f4f185 "can: peak_usb: add support - bwh> for PEAK new CANFD USB adapters". -Bugs: -upstream: released (5.3-rc4) [30a8beeb3042f49d0537b7050fd21b490166a3d9] -4.19-upstream-stable: released (4.19.67) [9ce1b3eb5489416338b2fb2b40f30f0d425700b4] -4.9-upstream-stable: released (4.9.190) [127ab64c38e21c55adf8781ca92f7dc9d1a9903e] -3.16-upstream-stable: N/A "Vulnerable code not present" -sid: released (5.2.9-1) -4.19-buster-security: released (4.19.67-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/active/CVE-2019-19536 b/active/CVE-2019-19536 deleted file mode 100644 index 51287c7b..00000000 --- a/active/CVE-2019-19536 +++ /dev/null @@ -1,13 +0,0 @@ -Description: can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.3-rc4) [ead16e53c2f0ed946d82d4037c630e2f60f4ab69] -4.19-upstream-stable: released (4.19.67) [cab569a44a524709d95bbd88700860ac45e5d5cf] -4.9-upstream-stable: released (4.9.190) [0cad79bfb5aa596b9449fe66b0edf69a8344326c] -3.16-upstream-stable: released (3.16.78) [06d7546f7b115a266a9bb81887479f38e166964e] -sid: released (5.2.9-1) -4.19-buster-security: released (4.19.67-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19537 b/active/CVE-2019-19537 deleted file mode 100644 index 3d583de4..00000000 --- a/active/CVE-2019-19537 +++ /dev/null @@ -1,13 +0,0 @@ -Description: USB: core: Fix races in character device registration and deregistraion -References: - http://www.openwall.com/lists/oss-security/2019/12/03/4 -Notes: -Bugs: -upstream: released (5.3-rc5) [303911cfc5b95d33687d9046133ff184cf5043ff] -4.19-upstream-stable: released (4.19.68) [7f52d6d2a82df15d7ea01d69d0943d2abc201b43] -4.9-upstream-stable: released (4.9.190) [741b832658b98463d619fe4c320f8ab11b2ad4ee] -3.16-upstream-stable: released (3.16.78) [7e0af4e53ee2cf9b5e4ee761bd8dc4f25a9c885a] -sid: released (5.2.17-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19767 b/active/CVE-2019-19767 deleted file mode 100644 index a8d31a7d..00000000 --- a/active/CVE-2019-19767 +++ /dev/null @@ -1,16 +0,0 @@ -Description: ext4: add more paranoia checking in ext4_expand_extra_isize handling -References: - https://bugzilla.kernel.org/show_bug.cgi?id=205609 - https://bugzilla.kernel.org/show_bug.cgi?id=205707 -Notes: - bwh> Apparently introduced in 2.6.23 by commit 6dd4ee7cab7e "ext4: - bwh> Expand extra_inodes space per the s_{want,min}_extra_isize fields". -Bugs: -upstream: released (5.5-rc1) [4ea99936a1630f51fc3a2d61a58ec4a1c4b7d55a] -4.19-upstream-stable: released (4.19.88) [e91cce02f3025da559468729ea0ad9dea242d3eb] -4.9-upstream-stable: released (4.9.211) [8e508ac2e7278759259fd818603af02e8e3a64f6] -3.16-upstream-stable: released (3.16.81) [f01bb82f5cde15ba2f6fc17cf706196a32aecd45] -sid: released (5.3.15-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) [bugfix/all/ext4-add-more-paranoia-checking-in-ext4_expand_extra_isize-handling.patch] -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19922 b/active/CVE-2019-19922 deleted file mode 100644 index cfe4f6e3..00000000 --- a/active/CVE-2019-19922 +++ /dev/null @@ -1,18 +0,0 @@ -Description: sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices -References: - https://github.com/kubernetes/kubernetes/issues/67577 - https://relistan.com/the-kernel-may-be-slowing-down-your-app - https://bugzilla.kernel.org/show_bug.cgi?id=198197 -Notes: - bwh> Apparently introduced in 4.18 by commit 512ac999d275 "sched/fair: - bwh> Fix bandwidth timer clock drift condition", which was backported to - bwh> 3.16 and 4.14. -Bugs: -upstream: released (5.4-rc1) [de53fd7aedb100f03e5d2231cfce0e4993282425] -4.19-upstream-stable: released (4.19.84) [502bd151448c2c76a927b26783e5538875c534ff] -4.9-upstream-stable: N/A "Vulnerability introduced later" -3.16-upstream-stable: released (3.16.81) [61749beefb4a12af7d91424bcd58ffdc072dad63] -sid: released (5.3.9-1) -4.19-buster-security: released (4.19.87-1) -4.9-stretch-security: N/A "Vulnerability introduced later" -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-19965 b/active/CVE-2019-19965 deleted file mode 100644 index e9162fed..00000000 --- a/active/CVE-2019-19965 +++ /dev/null @@ -1,15 +0,0 @@ -Description: scsi: libsas: stop discovering if oob mode is disconnected -References: -Notes: - carnil> Fixed as well in 5.4.9. - bwh> Apparently introduced in 2.6.19 by commit 2908d778ab3e "[SCSI] - bwh> aic94xx: new driver" before the function was moved into libsas. -Bugs: -upstream: released (5.5-rc2) [f70267f379b5e5e11bdc5d72a56bf17e5feed01f] -4.19-upstream-stable: released (4.19.94) [8b9bf467061bc89ccf4a43be637e08d8a70fd76d] -4.9-upstream-stable: released (4.9.209) [8febe765539fbcc7d47e4e2ad44a0bcb2adbf02b] -3.16-upstream-stable: released (3.16.81) [f4e74a1371c84cca35e53afda50759e2d44e0507] -sid: released (5.4.13-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/active/CVE-2019-20096 b/active/CVE-2019-20096 deleted file mode 100644 index a01ae573..00000000 --- a/active/CVE-2019-20096 +++ /dev/null @@ -1,12 +0,0 @@ -Description: dccp: Fix memleak in __feat_register_sp -References: -Notes: -Bugs: -upstream: released (5.1-rc4) [1d3ff0950e2b40dc861b1739029649d03f591820] -4.19-upstream-stable: released (4.19.97) [e58c590c772eb5dc5a3603c5aef4148f47ab2e20] -4.9-upstream-stable: released (4.9.211) [33cab7a0a84d35908c75c4b46c88769be7902556] -3.16-upstream-stable: released (3.16.72) [6f5a5f7e229e3ec71d729f3fd4479a11a0a21fd8] -sid: released (5.2.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: released (4.9.210-1) [bugfix/all/dccp-fix-memleak-in-__feat_register_sp.patch] -3.16-jessie-security: released (3.16.72-1) diff --git a/active/CVE-2019-2215 b/active/CVE-2019-2215 deleted file mode 100644 index 91b06fa8..00000000 --- a/active/CVE-2019-2215 +++ /dev/null @@ -1,15 +0,0 @@ -Description: Use-After-Free in Binder driver -References: - https://bugs.chromium.org/p/project-zero/issues/detail?id=1942 - https://googleprojectzero.blogspot.com/2019/11/bad-binder-android-in-wild-exploit.html -Notes: - bwh> Although the fix commit is marked "# 4.14", the bug is much older. -Bugs: -upstream: released (4.16-rc1) [f5cb779ba16334b45ba8946d6bfa6d9834d1527f] -4.19-upstream-stable: N/A "Fixed before branching point" -4.9-upstream-stable: released (4.9.196) [a494a71146a1cf3f48bb94cf33981db1f027e6a0] -3.16-upstream-stable: released (3.16.79) [3a593dd8bd7505f9acbc7b6f8928ec6b7978c125] -sid: released (4.15.4-1) -4.19-buster-security: N/A "Fixed before branching point" -4.9-stretch-security: released (4.9.210-1) -3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2018-20976 b/retired/CVE-2018-20976 new file mode 100644 index 00000000..0ebf974f --- /dev/null +++ b/retired/CVE-2018-20976 @@ -0,0 +1,12 @@ +Description: xfs: clear sb->s_fs_info on mount failure +References: +Notes: +Bugs: +upstream: released (4.18-rc1) [c9fbd7bbc23dbdd73364be4d045e5d3612cf6e82] +4.19-upstream-stable: N/A "Fixed before branching point" +4.9-upstream-stable: released (4.9.197) [e6e3f36b1ac9c439d3bc0b2c2aaf1663ad705ac0] +3.16-upstream-stable: released (3.16.74) [bf3878994377a97143f5f6b6e60a18f9b76e0476] +sid: released (4.18.6-1) +4.19-buster-security: N/A "Fixed before branching point" +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.74-1) diff --git a/retired/CVE-2018-21008 b/retired/CVE-2018-21008 new file mode 100644 index 00000000..11f060a4 --- /dev/null +++ b/retired/CVE-2018-21008 @@ -0,0 +1,13 @@ +Description: rsi: add fix for crash during assertions +References: +Notes: + bwh> Apparently introduced in 3.15 when rsi driver was added. +Bugs: +upstream: released (4.18-rc1) [abd39c6ded9db53aa44c2540092bdd5fb6590fa8] +4.19-upstream-stable: N/A "Fixed before branching point" +4.9-upstream-stable: released (4.9.211) [65b32fd4eabc5209019894627b1bda65611fd1cb] +3.16-upstream-stable: released (3.16.74) [fd56118648c89adbd7a64bc8e3e26ac4871d1c1a] +sid: released (4.18.6-1) +4.19-buster-security: N/A "Fixed before branching point" +4.9-stretch-security: released (4.9.210-1) [bugfix/all/rsi-add-fix-for-crash-during-assertions.patch] +3.16-jessie-security: released (3.16.74-1) diff --git a/retired/CVE-2018-ebpf-filter-dos b/retired/CVE-2018-ebpf-filter-dos new file mode 100644 index 00000000..20753e96 --- /dev/null +++ b/retired/CVE-2018-ebpf-filter-dos @@ -0,0 +1,13 @@ +Description: Ability to fill entire module space with eBPF JIT socket filters +References: +Notes: + bwh> This should be minor for Debian because we don't enable JIT by default. +Bugs: +upstream: released (4.20-rc1) [ede95a63b5e84ddeea6b0c473b36ab8bfd8c6ce3] +4.19-upstream-stable: released (4.19.47) [43caa29c99db5a41b204e8ced01b00e151335ca8] +4.9-upstream-stable: released (4.9.190) [c98446e1bab6253ddce7144cc2a91c400a323839] +3.16-upstream-stable: N/A "eBPF not implemented" +sid: released (5.2.6-1) +4.19-buster-security: released (4.19.67-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "eBPF not implemented" diff --git a/retired/CVE-2019-0136 b/retired/CVE-2019-0136 new file mode 100644 index 00000000..d8fa5a9e --- /dev/null +++ b/retired/CVE-2019-0136 @@ -0,0 +1,20 @@ +Description: Insufficient access control in the Intel(R) PROSet/Wireless WiFi Software driver before version 21.10 may allow an unauthenticated user to potentially enable denial of service via adjacent access. +References: + https://people.canonical.com/~ubuntu-security/cve/2019/CVE-2019-0136.html +Notes: + carnil> the second commit 79c92ca42b5a ("mac80211: handle + carnil> deauthentication/disassociation from TDLS peer") is not applied + carnil> to older branches and might need investigation if applicable. + bwh> I think commit 79c92ca42b5a is relevant to older branches and have + bwh> backported it to 3.16. + carnil> Backport request for 4.9: https://lore.kernel.org/stable/20190927115711.GA8961@eldamar.local/ + bwh> stretch still only has the first commit. +Bugs: +upstream: released (v5.2-rc6) [588f7d39b3592a36fb7702ae3b8bdd9be4621e2f, 79c92ca42b5a3e0ea172ea2ce8df8e125af237da] +4.19-upstream-stable: released (4.19.56) [0e879ef1cb5baddebe1f12a9a3940a87d8e61558, 1e1007ac47d85dacf6d45821a2870b6268499700] +4.9-upstream-stable: released (4.9.195) [9f0f5ff93ed0205a90f11103e9937f3c0417cd4b, 7b1f4ffab73d9319b8132bbf5f4a0e2110a98bde] +3.16-upstream-stable: released (3.16.74) [62909f7d0b1360ddb147bae8f546228dd93588e1, 8c2981482a9a1b8910dd0b4365b53db1a056ae66] +sid: released (5.2.6-1) +4.19-buster-security: released (4.19.67-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.74-1) diff --git a/retired/CVE-2019-10220 b/retired/CVE-2019-10220 new file mode 100644 index 00000000..be260f16 --- /dev/null +++ b/retired/CVE-2019-10220 @@ -0,0 +1,23 @@ +Description: CIFS: Relative paths injection in directory entry lists +References: + https://bugzilla.redhat.com/show_bug.cgi?id=1741727 + https://bugzilla.suse.com/show_bug.cgi?id=1144903 + https://bugzilla.samba.org/show_bug.cgi?id=14072 +Notes: + carnil> Needed a followup c512c6918719 ("uaccess: implement a proper + carnil> unsafe_copy_to_user() and switch filldir over to it"), cf. + carnil> https://lore.kernel.org/linux-fsdevel/20191006222046.GA18027@roeck-us.net/ + carnil> which landed in 5.4-rc3. + bwh> Although this was reported against CIFS, it seems to be a general + bwh> vulnerability for all filesystems dealing with untrusted servers or + bwh> storage. Thankfully the fix is also general. + bwh> The changes to uaccess in filldir are *not* required. +Bugs: +upstream: released (5.4-rc4) [8a23eb804ca4f2be909e372cf5a9e7b30ae476cd, b9959c7a347d6adbb558fba7e36e9fef3cba3b07] +4.19-upstream-stable: released (4.19.93) [40696eb2bce798c4764886fbc576426bd5c4cc3c, 0643c3d694ad9f1e5cb0bc7a487bf9f86a5eaf75] +4.9-upstream-stable: released (4.9.208) [89f58402e7088d38365f227a7943b1b3fed7489b, 1944687187713590a8722f3f1dfd1cd90e7cbde6] +3.16-upstream-stable: released (3.16.81) [8b85eda7dac918a308e6e1d9137887930e80827a, 0ad70158f3c02e373e17377237b85e43f06d6752] +sid: released (5.3.9-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-14814 b/retired/CVE-2019-14814 new file mode 100644 index 00000000..4774f8c0 --- /dev/null +++ b/retired/CVE-2019-14814 @@ -0,0 +1,16 @@ +Description: Heap Overflow in mwifiex_set_uap_rates() function +References: + https://www.openwall.com/lists/oss-security/2019/08/28/1 + https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@gmail.com/ +Notes: + bwh> Introduced in 3.7 by commit a3c2c4f6d8bc "mwifiex: parse rate info + bwh> for AP". +Bugs: +upstream: released (5.3) [7caac62ed598a196d6ddf8d9c121e12e082cac3a] +4.19-upstream-stable: released (4.19.75) [941431c491a68e0428bdfb46bbe4cbc52f7bfabb] +4.9-upstream-stable: released (4.9.194) [21dfacaf201ed13af70a8bd3e66bcf18cdb63b35] +3.16-upstream-stable: released (3.16.74) [fb8186b15518423646f0e2105c34b3e620623b4e] +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.74-1) diff --git a/retired/CVE-2019-14815 b/retired/CVE-2019-14815 new file mode 100644 index 00000000..ddeeb10f --- /dev/null +++ b/retired/CVE-2019-14815 @@ -0,0 +1,20 @@ +Description: Heap Overflow in mwifiex_set_wmm_params() function +References: + https://www.openwall.com/lists/oss-security/2019/08/28/1 + https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@gmail.com/ +Notes: + bwh> Introduced in 4.10 by commit 113630b581d6 "mwifiex: vendor_ie length + bwh> check for parse WMM IEs". + carnil> The bounds-check in mwifiex_set_wmm_paramsare still applied as + carnil> well in older versions e.g. 4.9.194. Put the state again in + carnil> needed for 4.9-stretch-security but just to recheck if this is + carnil> really not needed to track for CVE-2019-14815. +Bugs: +upstream: released (5.3) [7caac62ed598a196d6ddf8d9c121e12e082cac3a] +4.19-upstream-stable: released (4.19.75) [941431c491a68e0428bdfb46bbe4cbc52f7bfabb] +4.9-upstream-stable: released (4.9.194) [21dfacaf201ed13af70a8bd3e66bcf18cdb63b35] +3.16-upstream-stable: N/A "Vulnerability introduced later" +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/retired/CVE-2019-14816 b/retired/CVE-2019-14816 new file mode 100644 index 00000000..f115d518 --- /dev/null +++ b/retired/CVE-2019-14816 @@ -0,0 +1,16 @@ +Description: Heap Overflow in mwifiex_update_vs_ie() function +References: + https://www.openwall.com/lists/oss-security/2019/08/28/1 + https://lore.kernel.org/linux-wireless/20190828020751.13625-1-huangwenabc@gmail.com/ +Notes: + bwh> Introduced in 3.6 by commit 2152fe9c2fa4 "mwifiex: parse WPS IEs from + bwh> beacon_data". +Bugs: +upstream: released (5.3) [7caac62ed598a196d6ddf8d9c121e12e082cac3a] +4.19-upstream-stable: released (4.19.75) [941431c491a68e0428bdfb46bbe4cbc52f7bfabb] +4.9-upstream-stable: released (4.9.194) [21dfacaf201ed13af70a8bd3e66bcf18cdb63b35] +3.16-upstream-stable: released (3.16.74) [fb8186b15518423646f0e2105c34b3e620623b4e] +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.74-1) diff --git a/retired/CVE-2019-14895 b/retired/CVE-2019-14895 new file mode 100644 index 00000000..ddcce639 --- /dev/null +++ b/retired/CVE-2019-14895 @@ -0,0 +1,18 @@ +Description: Heap overflow in mwifiex_process_country_ie() function of Marvell Wifi driver +References: + https://www.openwall.com/lists/oss-security/2019/11/22/1 + https://patchwork.kernel.org/patch/11256477/ +Notes: + bwh> Introduced in 3.7 by commit e89e2da29b7e "mwifiex: use country ie of + bwh> requested AP while associating". Fixed by commit 3d94a4a8373b + bwh> "mwifiex: fix possible heap overflow in mwifiex_process_country_ie()". + carnil> Fixed as well in 5.4.12. +Bugs: +upstream: released (5.5-rc3) [3d94a4a8373bf5f45cf5f939e88b8354dbf2311b] +4.19-upstream-stable: released (4.19.96) [0aa8632c57930243bea6fa4ebcbff8fac089e664] +4.9-upstream-stable: released (4.9.210) [efa99b6f3844bd20d46c8afd78f92a0161a4718e] +3.16-upstream-stable: released (3.16.81) [3b2f9bd867e1a288b470da440992a908c5972644] +sid: released (5.4.13-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-15030 b/retired/CVE-2019-15030 new file mode 100644 index 00000000..a42adc8f --- /dev/null +++ b/retired/CVE-2019-15030 @@ -0,0 +1,20 @@ +Description: powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction +References: +Notes: + carnil> Commit fixes f48e91e87e67 ("powerpc/tm: Fix FP and VMX register + carnil> corruption") but that commit was backported as well to older + carnil> versions than 4.12, so the CC to stable@v.k.o does not seem + carnil> completely correct. It was included as well in 4.9.30. + carnil> Fix can be defered to point release when updating to new + carnil> upstream stable versions as we disable + carnil> CONFIG_PPC_TRANSACTIONAL_MEM since 5.2.6-1 (sid), 4.19.67-2 + carnil> (buster) and 4.9.184-1 (stretch). +Bugs: +upstream: released (5.3-rc8) [8205d5d98ef7f155de211f5e2eb6ca03d95a5a60] +4.19-upstream-stable: released (4.19.73) [47a0f70d7d9ac3d6b1a96b312d07bc67af3834e9] +4.9-upstream-stable: released (4.9.193) [acdf558ef62ceb71938d87f5b700b7ecc0bbee90] +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-15031 b/retired/CVE-2019-15031 new file mode 100644 index 00000000..a915602f --- /dev/null +++ b/retired/CVE-2019-15031 @@ -0,0 +1,18 @@ +Description: powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts +References: + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1843533 +Notes: + carnil> Commit fixes a7771176b439 ("powerpc: Don't enable FP/Altivec if + carnil> not checkpointed") in 4.15-rc1. Fix can be defered to point + carnil> release when updating to new upstream stable versions as we + carnil> disable CONFIG_PPC_TRANSACTIONAL_MEM since 5.2.6-1 (sid), + carnil> 4.19.67-2 (buster). +Bugs: +upstream: released (5.3-rc8) [a8318c13e79badb92bc6640704a64cc022a6eb97] +4.19-upstream-stable: released (4.19.73) [569775bd536416ed9049aa580d9f89a0b4307d60] +4.9-upstream-stable: N/A "Vulnerable code introduced later" +3.16-upstream-stable: N/A "Vulnerable code introduced later" +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code introduced later" +3.16-jessie-security: N/A "Vulnerable code introduced later" diff --git a/retired/CVE-2019-15098 b/retired/CVE-2019-15098 new file mode 100644 index 00000000..1c826f3b --- /dev/null +++ b/retired/CVE-2019-15098 @@ -0,0 +1,16 @@ +Description: Fix a NULL-ptr-deref bug in ath6kl_usb_alloc_urb_from_pipe +References: + https://lore.kernel.org/linux-wireless/20190804002905.11292-1-benquike@gmail.com/T/#u + https://syzkaller.appspot.com/bug?id=cd8b9cfe50a0bf36ee19eda2d7e2e06843dfbeaf +Notes: + bwh> Introduced in Linux 3.5 by commit 9cbee358687e "ath6kl: add full USB + bwh> support". +Bugs: +upstream: released (5.4-rc1) [39d170b3cb62ba98567f5c4f40c27b5864b304e5] +4.19-upstream-stable: released (4.19.82) [696da02259463ea634821e117088f82afe7bf851] +4.9-upstream-stable: released (4.9.199) [3c7f02d13b8d72dbb1dd9b0fe858459d263b1fbd] +3.16-upstream-stable: released (3.16.77) [3e8e6f9a952c9a7e0be92518906dcdb7c8d1ca29] +sid: released (5.3.7-1) [bugfix/all/ath6kl-fix-a-NULL-ptr-deref-bug-in-ath6kl_usb_alloc_.patch] +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-15099 b/retired/CVE-2019-15099 new file mode 100644 index 00000000..ed10fdc3 --- /dev/null +++ b/retired/CVE-2019-15099 @@ -0,0 +1,15 @@ +Description: Fix a NULL-ptr-deref bug in ath10k_usb_alloc_urb_from_pipe +References: + https://lore.kernel.org/linux-wireless/20190804003101.11541-1-benquike@gmail.com/T/#u +Notes: + bwh> Introduced in 4.14 by commit 4db66499df91 "ath10k: add initial USB + bwh> support". +Bugs: +upstream: released (5.5-rc1) [bfd6e6e6c5d2ee43a3d9902b36e01fc7527ebb27] +4.19-upstream-stable: released (4.19.87) [f0cfe98332d650f31b462207d63c496b4cedaee2] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-15217 b/retired/CVE-2019-15217 new file mode 100644 index 00000000..88067cdb --- /dev/null +++ b/retired/CVE-2019-15217 @@ -0,0 +1,15 @@ +Description: media: usb:zr364xx:Fix KASAN:null-ptr-deref Read in zr364xx_vidioc_querycap +References: + https://syzkaller.appspot.com/bug?id=9c0c178c24d828a7378f483309001329750aad64 +Notes: + bwh> Introduced in 2.6.32 by commit ccbf035ae5de "V4L/DVB (12278): zr364xx: + bwh> implement V4L2_CAP_STREAMING". +Bugs: +upstream: released (5.3-rc1) [5d2e73a5f80a5b5aff3caf1ec6d39b5b3f54b26e] +4.19-upstream-stable: released (4.19.97) [0648766cb7d336e5932278c316aef6aac35d60ab] +4.9-upstream-stable: released (4.9.211) [6ba34f5de2a45050729836e3d48ed10ee53d0276] +3.16-upstream-stable: released (3.16.77) [4accfbf9527ed191513f4d2d738caf15ad4e8657] +sid: released (5.2.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) [bugfix/all/media-usb-zr364xx-fix-kasan-null-ptr-deref-read-in-z.patch] +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-15291 b/retired/CVE-2019-15291 new file mode 100644 index 00000000..ebf560e8 --- /dev/null +++ b/retired/CVE-2019-15291 @@ -0,0 +1,13 @@ +Description: general protection fault in flexcop_usb_probe +References: + https://syzkaller.appspot.com/bug?id=c0203bd72037d07493f4b7562411e4f5f4553a8f +Notes: +Bugs: +upstream: released (5.5-rc1) [1b976fc6d684e3282914cdbe7a8d68fdce19095c] +4.19-upstream-stable: released (4.19.87) [8b42c263ec1a348bf098e6255407486c1bf17ece] +4.9-upstream-stable: released (4.9.204) [2ab1da610f23d72ab53c3951876fa44ed85e1f99] +3.16-upstream-stable: released (3.16.79) [470a2d36f614f40b7f032071cfa6662dfcc1eda4] +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-15504 b/retired/CVE-2019-15504 new file mode 100644 index 00000000..59b824d3 --- /dev/null +++ b/retired/CVE-2019-15504 @@ -0,0 +1,16 @@ +Description: Fix a double free bug in rsi_91x_deinit +References: + https://lore.kernel.org/lkml/20190819220230.10597-1-benquike@gmail.com/ +Notes: + carnil> Possibly introduced only with a1854fae1414 ("rsi: improve RX + carnil> packet handling in USB interface") in 4.17-rc1. + bwh> I agree that commit a1854fae1414 introduced this. +Bugs: +upstream: released (5.3) [8b51dc7291473093c821195c4b6af85fadedbc2f] +4.19-upstream-stable: released (4.19.74) [3622d621e9beca76d53cd3007eb7b1d6e724716b] +4.9-upstream-stable: N/A "Vulnerability introduced later" +3.16-upstream-stable: N/A "Vulnerability introduced later" +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerability introduced later" +3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/retired/CVE-2019-15505 b/retired/CVE-2019-15505 new file mode 100644 index 00000000..96ed4cf0 --- /dev/null +++ b/retired/CVE-2019-15505 @@ -0,0 +1,16 @@ +Description: media: technisat-usb2: break out of loop at end of buffer +References: + https://git.linuxtv.org/media_tree.git/commit/?id=0c4df39e504bf925ab666132ac3c98d6cbbe380b + https://lore.kernel.org/linux-media/20190821104408.w7krumcglxo6fz5q@gofer.mess.org/ + https://lore.kernel.org/lkml/b9b256cb-95f2-5fa1-9956-5a602a017c11@gmail.com/ +Notes: + bwh> Apparently introduced in 2.6.39 when technisat-usb2 driver was added. +Bugs: +upstream: released (5.4-rc1) [0c4df39e504bf925ab666132ac3c98d6cbbe380b] +4.19-upstream-stable: released (4.19.75) [b841a9f58d9c778d8c2c5f636dc06a53b9a47fa1] +4.9-upstream-stable: released (4.9.194) [994c6dcb4307759d440b8031e140d343b8611481] +3.16-upstream-stable: released (3.16.77) [2389a6543a1c2b3bd1ab5dae04d23c3ed9c95752] +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-15917 b/retired/CVE-2019-15917 new file mode 100644 index 00000000..8db4a493 --- /dev/null +++ b/retired/CVE-2019-15917 @@ -0,0 +1,15 @@ +Description: Bluetooth: hci_ldisc: Postpone HCI_UART_PROTO_READY bit set in hci_uart_set_proto() +References: +Notes: + bwh> Maybe introduced in 4.7 by commit 84cb3df02aea "Bluetooth: hci_ldisc: + bwh> Fix null pointer derefence in case of early data", but I suspect a + bwh> similar issue existed before that too. +Bugs: +upstream: released (5.1-rc1) [56897b217a1d0a91c9920cb418d6b3fe922f590a] +4.19-upstream-stable: released (4.19.32) [e365b94086f9dec02ddfcc193dcad72858c6d973] +4.9-upstream-stable: released (4.9.202) [3858f013de0ae5a19b8276944e12fd01b0cac979] +3.16-upstream-stable: released (3.16.74) [a79897227b81d588130813e83084b836733cb146] +sid: released (4.19.37-1) +4.19-buster-security: N/A "Fixed before branching point" +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.74-1) diff --git a/retired/CVE-2019-15918 b/retired/CVE-2019-15918 new file mode 100644 index 00000000..78e685c6 --- /dev/null +++ b/retired/CVE-2019-15918 @@ -0,0 +1,14 @@ +Description: cifs: Fix lease buffer length error +References: +Notes: + bwh> Introduced in 4.14 by commit 9764c02fcbad "SMB3: Add support for + bwh> multidialect negotiate (SMB2.1 and later)". +Bugs: +upstream: released (5.1-rc6) [b57a55e2200ede754e4dc9cce4ba9402544b9365] +4.19-upstream-stable: released (4.19.73) [4061e662c8e9f5fb796b05fd2ab58fed8cd16d59] +4.9-upstream-stable: N/A "Vulnerability introduced later" +3.16-upstream-stable: N/A "Vulnerability introduced later" +sid: released (5.2.6-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerability introduced later" +3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/retired/CVE-2019-16714 b/retired/CVE-2019-16714 new file mode 100644 index 00000000..aabd14e0 --- /dev/null +++ b/retired/CVE-2019-16714 @@ -0,0 +1,13 @@ +Description: net/rds: Fix info leak in rds6_inc_info_copy() +References: +Notes: + bwh> Introduced by commit b7ff8b1036f0 "rds: Extend RDS API for IPv6 support" +Bugs: +upstream: released (5.3-rc7) [7d0a06586b2686ba80c4a2da5f91cb10ffbea736] +4.19-upstream-stable: released (4.19.72) [9484203d254d5e41f7120c15122b789f96647886] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-16746 b/retired/CVE-2019-16746 new file mode 100644 index 00000000..9362db4a --- /dev/null +++ b/retired/CVE-2019-16746 @@ -0,0 +1,13 @@ +Description: nl80211: validate beacon head +References: + https://marc.info/?l=linux-wireless&m=156901391225058&w=2 +Notes: +Bugs: +upstream: released (5.4-rc2) [f88eb7c0d002a67ef31aeb7850b42ff69abc46dc] +4.19-upstream-stable: released (4.19.79) [1bd17a737c9e7e91483d9a603528b0e6d4c772f8] +4.9-upstream-stable: released (4.9.197) [a873afd7d888f7349bfabc9191afeb20eb1d3a45] +3.16-upstream-stable: released (3.16.79) [9eec2aca63328997846b52e91e88dab94ccd1414] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-17052 b/retired/CVE-2019-17052 new file mode 100644 index 00000000..1a7b8117 --- /dev/null +++ b/retired/CVE-2019-17052 @@ -0,0 +1,12 @@ +Description: ax25: enforce CAP_NET_RAW for raw sockets +References: +Notes: +Bugs: +upstream: released (5.4-rc1) [0614e2b73768b502fc32a75349823356d98aae2c] +4.19-upstream-stable: released (4.19.77) [6f0f18e532693ecc1e0c7938e0d63531ea62bc3e] +4.9-upstream-stable: released (4.9.195) [73b8d26c842a5a3be34a321beab1f97939d9794b] +3.16-upstream-stable: released (3.16.77) [2c675dab816278a1724c1e93b384c2f05a11cb31] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-17053 b/retired/CVE-2019-17053 new file mode 100644 index 00000000..348c0b8e --- /dev/null +++ b/retired/CVE-2019-17053 @@ -0,0 +1,12 @@ +Description: ieee802154: enforce CAP_NET_RAW for raw sockets +References: +Notes: +Bugs: +upstream: released (5.4-rc1) [e69dbd4619e7674c1679cba49afd9dd9ac347eef] +4.19-upstream-stable: released (4.19.77) [dd651ab7a11436f787aed0a987c85864b261ff19] +4.9-upstream-stable: released (4.9.195) [ddca1f39c8980cb19db5ea6d51b8549288a7421b] +3.16-upstream-stable: released (3.16.77) [b8a15d59a9b26a734f6d8d5f10376f336f7d021b] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-17054 b/retired/CVE-2019-17054 new file mode 100644 index 00000000..3360f5df --- /dev/null +++ b/retired/CVE-2019-17054 @@ -0,0 +1,12 @@ +Description: appletalk: enforce CAP_NET_RAW for raw sockets +References: +Notes: +Bugs: +upstream: released (5.4-rc1) [6cc03e8aa36c51f3b26a0d21a3c4ce2809c842ac] +4.19-upstream-stable: released (4.19.77) [6fbf866276089853727dd9b31f1d251e61dde367] +4.9-upstream-stable: released (4.9.195) [08d2af9358c1937acf97417dba9a03a40149c4d2] +3.16-upstream-stable: released (3.16.77) [2d4020439bd19f2a498a7fccd8755521a90b2886] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-17055 b/retired/CVE-2019-17055 new file mode 100644 index 00000000..b6120cf3 --- /dev/null +++ b/retired/CVE-2019-17055 @@ -0,0 +1,12 @@ +Description: mISDN: enforce CAP_NET_RAW for raw sockets +References: +Notes: +Bugs: +upstream: released (5.4-rc1) [b91ee4aa2a2199ba4d4650706c272985a5a32d80] +4.19-upstream-stable: released (4.19.77) [50dddec689cb2105f6bccf4a2c6fe43dcc3295d7] +4.9-upstream-stable: released (4.9.195) [bb439ee217acbf7835af634f08875540c514632f] +3.16-upstream-stable: released (3.16.77) [f49bd6510620b9cd434b87bea639f07dfde56f09] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-17056 b/retired/CVE-2019-17056 new file mode 100644 index 00000000..fb010058 --- /dev/null +++ b/retired/CVE-2019-17056 @@ -0,0 +1,12 @@ +Description: nfc: enforce CAP_NET_RAW for raw sockets +References: +Notes: +Bugs: +upstream: released (5.4-rc1) [3a359798b176183ef09efb7a3dc59abad1cc7104] +4.19-upstream-stable: released (4.19.77) [33fe1f517e29566d842535038be227c71a4bd54d] +4.9-upstream-stable: released (4.9.195) [45a9e9bc5d6742988df799dafbf26dca8e0dada3] +3.16-upstream-stable: released (3.16.77) [bc3d2e9cfdc5c1b7e5ed34eb5279e47d462b4d5c] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-17075 b/retired/CVE-2019-17075 new file mode 100644 index 00000000..54044d80 --- /dev/null +++ b/retired/CVE-2019-17075 @@ -0,0 +1,15 @@ +Description: cxgb4: do not dma memory off of the stack +References: + https://lore.kernel.org/lkml/20191001165611.GA3542072@kroah.com/ +Notes: + bwh> I believe this "worked" on Debian supported architectures until 4.9 + bwh> introduced vmapped stacks for amd64. +Bugs: +upstream: released (5.4-rc3) [3840c5b78803b2b6cc1ff820100a74a092c40cbb] +4.19-upstream-stable: released (4.19.81) [27414f90ff6e1d7f6657e4a820b04a7b2d760272] +4.9-upstream-stable: released (4.9.198) [84f5b67df81a9f333afa81855f6fa3fdcd954463] +3.16-upstream-stable: ignored "Not a problem in practice" +sid: released (5.3.7-1) [bugfix/all/RDMA-cxgb4-Do-not-dma-memory-off-of-the-stack.patch] +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: ignored "Not a problem in practice" diff --git a/retired/CVE-2019-17133 b/retired/CVE-2019-17133 new file mode 100644 index 00000000..9c861cac --- /dev/null +++ b/retired/CVE-2019-17133 @@ -0,0 +1,14 @@ +Description: cfg80211: wext: avoid copying malformed SSIDs +References: + https://marc.info/?l=linux-wireless&m=157018270915487&w=2 +Notes: + carnil> In 5.3.x fixed in 5.3.8. +Bugs: +upstream: released (5.4-rc4) [4ac2813cc867ae563a1ba5a9414bfb554e5796fa] +4.19-upstream-stable: released (4.19.81) [73c066a9552a6d33ed7de002855337d1c966e8ce] +4.9-upstream-stable: released (4.9.198) [49d84740f8a7040354ef93bf5915a4b3e651e71b] +3.16-upstream-stable: released (3.16.77) [e70efb76ea2eb9f08dc627d93d35a8e5c065346d] +sid: released (5.3.9-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-17666 b/retired/CVE-2019-17666 new file mode 100644 index 00000000..c1352311 --- /dev/null +++ b/retired/CVE-2019-17666 @@ -0,0 +1,13 @@ +Description: rtlwifi: Fix potential overflow on P2P code +References: + https://lkml.org/lkml/2019/10/16/1226 +Notes: +Bugs: +upstream: released (5.4-rc6) [8c55dedb795be8ec0cf488f98c03a1c2176f7fb1] +4.19-upstream-stable: released (4.19.82) [64efcbc7a5a3c7a14e42ccf7b8a7e7667d672a33] +4.9-upstream-stable: released (4.9.199) [4a2fbab9e82fb662ad3419525742a1ddfc29a7b9] +3.16-upstream-stable: released (3.16.77) [b78c8469ceff4288d1092e22bfb277d3bd0d7147] +sid: released (5.3.9-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-18282 b/retired/CVE-2019-18282 new file mode 100644 index 00000000..caddd29c --- /dev/null +++ b/retired/CVE-2019-18282 @@ -0,0 +1,15 @@ +Description: net/flow_dissector: switch to siphash +References: +Notes: + bwh> The issue is not in flow dissector itself, but in the use of flow + bwh> dissector's hashing to generate flow labels. This was introduced + bwh> as an option in 3.17 and enabled by default in 4.3. +Bugs: +upstream: released (5.4-rc6) [55667441c84fa5e0911a0aac44fb059c15ba6da2] +4.19-upstream-stable: released (4.19.83) [558d2bdad5f6a0dd65ed7ed4f74419e826a97759] +4.9-upstream-stable: released (4.9.200) [1f94465d13ace2d4610c4eb2b362454ce2a9d87c] +3.16-upstream-stable: N/A "Vulnerability introduced later" +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/retired/CVE-2019-18660 b/retired/CVE-2019-18660 new file mode 100644 index 00000000..c3a34051 --- /dev/null +++ b/retired/CVE-2019-18660 @@ -0,0 +1,17 @@ +Description: powerpc: missing Spectre-RSB mitigation +References: + https://www.openwall.com/lists/oss-security/2019/11/27/1 +Notes: + carnil> Technically (resp. from CVE assignment point of view) the CVE + carnil> is solely for the missing Spectre-RSB mitigation and + carnil> 39e72bf96f58 ("powerpc/book3s64: Fix link stack flush on + carnil> context switch"). +Bugs: +upstream: released (5.5-rc1) [39e72bf96f5847ba87cc5bd7a3ce0fed813dc9ad, af2e8c68b9c5403f77096969c516f742f5bb29e0] +4.19-upstream-stable: released (4.19.87) [0a60d4bddc0ba6a7e06d10efa59f7861837860b0, 345712c95eec44bf414782b33e6d5a550fe62b3b] +4.9-upstream-stable: released (4.9.204) [113408cdaec11a6e34d4edabb134a335dd4896b3, e2c87b1ba04bd5042f6db0780ed55abaf4836378] +3.16-upstream-stable: ignored "No speculation mitigations available for powerpc" +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: ignored "powerpc not supported in LTS" diff --git a/retired/CVE-2019-18683 b/retired/CVE-2019-18683 new file mode 100644 index 00000000..108dda85 --- /dev/null +++ b/retired/CVE-2019-18683 @@ -0,0 +1,15 @@ +Description: media: vivid: Fix wrong locking that causes race conditions on streaming stop +References: + https://www.openwall.com/lists/oss-security/2019/11/02/1 + https://lore.kernel.org/lkml/20191102190327.24903-1-alex.popov@linux.com/ + https://lore.kernel.org/lkml/20191103221719.27118-1-alex.popov@linux.com/ +Notes: +Bugs: +upstream: released (5.5-rc1) [6dcd5d7a7a29c1e4b8016a06aed78cd650cd8c27] +4.19-upstream-stable: released (4.19.87) [467052f6ea5a51524992e43f02b543550495c391] +4.9-upstream-stable: released (4.9.204) [012a42dbc770d3e815cae536917245d74621c552] +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-18786 b/retired/CVE-2019-18786 new file mode 100644 index 00000000..29baeb75 --- /dev/null +++ b/retired/CVE-2019-18786 @@ -0,0 +1,15 @@ +Description: media: rcar_drif: fix a memory disclosure +References: + https://patchwork.linuxtv.org/patch/59542/ +Notes: + bwh> Introduced in 4.13 by commit 7625ee981af1 "[media] media: platform: + bwh> rcar_drif: Add DRIF support". +Bugs: +upstream: released (5.5-rc1) [d39083234c60519724c6ed59509a2129fd2aed41] +4.19-upstream-stable: released (4.19.92) [debdd16cbd99ffc767227685e2738e5b495b7c54] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.4.8-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-18806 b/retired/CVE-2019-18806 new file mode 100644 index 00000000..543a66de --- /dev/null +++ b/retired/CVE-2019-18806 @@ -0,0 +1,16 @@ +Description: net: qlogic: Fix memory leak in ql_alloc_large_buffers +References: +Notes: + bwh> I think this is an invalid issue and an incorrect fix; see + bwh> https://lore.kernel.org/stable/71577c0106fb9bcc28cff3f507e73bf2d3cb3713.camel@decadent.org.uk/ + bwh> and + bwh> https://lore.kernel.org/netdev/20191217015740.GA31381@decadent.org.uk/T/ +Bugs: +upstream: released (5.4-rc2) [1acb8f2a7a9f10543868ddd737e37424d5c36cf4] +4.19-upstream-stable: released (4.19.78) [9d0995cc268b4a431dbfb29db5cac36546732bc0] +4.9-upstream-stable: released (4.9.196) [3ae6d4c9473378d57bcad5a6e102c8ba42efd014] +3.16-upstream-stable: released (3.16.81) [e1db96134ab329054b73c4075949053e43ac7208] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: ignored "Invalid issue" diff --git a/retired/CVE-2019-18809 b/retired/CVE-2019-18809 new file mode 100644 index 00000000..c7168ce4 --- /dev/null +++ b/retired/CVE-2019-18809 @@ -0,0 +1,17 @@ +Description: media: usb: fix memory leak in af9005_identify_state +References: + https://github.com/torvalds/linux/commit/2289adbfa559050d2a38bcd9caac1c18b800e928 +Notes: + carnil> Fix not yet in Linus' tree. + bwh> Introduced in 4.9 by commit c58b84ee467b "[media] af9005: don't do DMA + bwh> on stack". Doesn't seem to have any security impact. + carnil> Fixed as well in 5.4.9. +Bugs: +upstream: released (5.5-rc1) [2289adbfa559050d2a38bcd9caac1c18b800e928] +4.19-upstream-stable: released (4.19.94) [d933de8115f3263fd50cf3b1f1dac2faff02fd89] +4.9-upstream-stable: released (4.9.209) [129139a26325d2274a226407d1e7b6f1eb40b456] +3.16-upstream-stable: N/A "Bug introduced later" +sid: released (5.4.13-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Bug introduced later" diff --git a/retired/CVE-2019-18813 b/retired/CVE-2019-18813 new file mode 100644 index 00000000..8b9958ff --- /dev/null +++ b/retired/CVE-2019-18813 @@ -0,0 +1,15 @@ +Description: usb: dwc3: pci: prevent memory leak in dwc3_pci_probe +References: +Notes: + bwh> Intrdocued in 4.19 by commit 1a7b12f69a94 "usb: dwc3: pci: Supply + bwh> device properties via driver data". No security impact since this + bwh> is on the probe path. Also not enabled in any Debian config. +Bugs: +upstream: released (5.4-rc6) [9bbfceea12a8f145097a27d7c7267af25893c060] +4.19-upstream-stable: released (4.19.84) [10eb9abd21bad2a9726f50557b38924cb8d81ccd] +4.9-upstream-stable: N/A "Bug introduced later" +3.16-upstream-stable: N/A "Bug introduced later" +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Bug introduced later" +3.16-jessie-security: N/A "Bug introduced later" diff --git a/retired/CVE-2019-19037 b/retired/CVE-2019-19037 new file mode 100644 index 00000000..5bd5a171 --- /dev/null +++ b/retired/CVE-2019-19037 @@ -0,0 +1,18 @@ +Description: ext4: Fix ext4_empty_dir() for directories with holes +References: + https://github.com/bobfuzzer/CVE/tree/master/CVE-2019-19037 + https://lore.kernel.org/stable/20191202170213.4761-2-jack@suse.cz/ +Notes: + carnil> commit fixes Fixes: 4e19d6b65fb4 ("ext4: allow directory + carnil> holes") which is in 5.3-rc1 but was backported to various other + carnil> stable trees in 5.2.4, 5.1.21, 4.19.62, 4.14.135 and 4.9.187 + carnil> already. +Bugs: +upstream: released (5.5-rc3) [64d4ce892383b2ad6d782e080d25502f91bf2a38] +4.19-upstream-stable: released (4.19.92) [1e62ac6b1307129c0f9ca68e9db4227239b4ab19] +4.9-upstream-stable: released (4.9.208) [dfcbd407f81e645601bccef8912af79b3d1ca87b] +3.16-upstream-stable: N/A "Vulnerability introduced later" +sid: released (5.4.8-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/retired/CVE-2019-19045 b/retired/CVE-2019-19045 new file mode 100644 index 00000000..b7a4185f --- /dev/null +++ b/retired/CVE-2019-19045 @@ -0,0 +1,13 @@ +Description: net/mlx5: prevent memory leak in mlx5_fpga_conn_create_cq +References: +Notes: + bwh> Introduced in 4.13 by commit 537a50574175. +Bugs: +upstream: released (5.4-rc6) [c8c2a057fdc7de1cd16f4baa51425b932a42eb39] +4.19-upstream-stable: released (4.19.84) [42de3a902443b64c6e3cf9c61d9cd6f30b2c0d67] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19048 b/retired/CVE-2019-19048 new file mode 100644 index 00000000..000ccced --- /dev/null +++ b/retired/CVE-2019-19048 @@ -0,0 +1,14 @@ +Description: virt: vbox: fix memory leak in hgcm_call_preprocess_linaddr +References: +Notes: + bwh> Introduced in 4.16 by commit 579db9d45cb4 "virt: Add vboxguest VMMDEV + bwh> communication code". +Bugs: +upstream: released (5.4-rc3) [e0b0cb9388642c104838fac100a4af32745621e2] +4.19-upstream-stable: released (4.19.82) [c2ea451f22f180e9e46225f54b5ec50c50bb639f] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.9-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19052 b/retired/CVE-2019-19052 new file mode 100644 index 00000000..1bca474c --- /dev/null +++ b/retired/CVE-2019-19052 @@ -0,0 +1,14 @@ +Description: can: gs_usb: gs_can_open(): prevent memory leak +References: +Notes: + bwh> Introduced in 3.16 by commit d08e973a77d1 "can: gs_usb: Added support + bwh> for the GS_USB CAN devices". +Bugs: +upstream: released (5.4-rc7) [fb5be6a7b4863ecc44963bb80ca614584b6c7817] +4.19-upstream-stable: released (4.19.84) [9289226f69822de0b716c0fbfc31db0283f14e2b] +4.9-upstream-stable: released (4.9.201) [b46a2067f36d7c5f2f259c4ed476359e6e9d668f] +3.16-upstream-stable: released (3.16.79) [f26d980434a06f44b693a26a87aa5300fa4016fd] +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19056 b/retired/CVE-2019-19056 new file mode 100644 index 00000000..2363c7ed --- /dev/null +++ b/retired/CVE-2019-19056 @@ -0,0 +1,15 @@ +Description: mwifiex: pcie: Fix memory leak in mwifiex_pcie_alloc_cmdrsp_buf +References: + https://github.com/torvalds/linux/commit/db8fd2cde93227e566a412cf53173ffa227998bc +Notes: + bwh> Introduced in 3.9 by commit fc3314609047 "mwifiex: use pci_alloc/ + bwh> free_consistent APIs for PCIe". +Bugs: +upstream: released (5.5-rc1) [db8fd2cde93227e566a412cf53173ffa227998bc] +4.19-upstream-stable: released (4.19.96) [f2bde0e9989e243345316e3c96b352ab94037340] +4.9-upstream-stable: released (4.9.210) [9bba4330671eaf1d21ac6025f950e7cca92f7aca] +3.16-upstream-stable: released (3.16.79) [f0eed3b1a34f1e7d8b2c06ad5ddf0ea60aea71ca] +sid: released (5.4.13-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19057 b/retired/CVE-2019-19057 new file mode 100644 index 00000000..19ce341f --- /dev/null +++ b/retired/CVE-2019-19057 @@ -0,0 +1,15 @@ +Description: mwifiex: pcie: Fix memory leak in mwifiex_pcie_init_evt_ring +References: + https://github.com/torvalds/linux/commit/d10dcb615c8e29d403a24d35f8310a7a53e3050c +Notes: + bwh> Introduced in 3.9 by commit fc3314609047 "mwifiex: use pci_alloc/ + bwh> free_consistent APIs for PCIe". +Bugs: +upstream: released (5.5-rc1) [d10dcb615c8e29d403a24d35f8310a7a53e3050c] +4.19-upstream-stable: released (4.19.92) [1b3e52db38471d5ac896eb9be111565e3734d5b5] +4.9-upstream-stable: released (4.9.208) [716156b896197824e55fc2f8244c8c43e0ed73e1] +3.16-upstream-stable: released (3.16.79) [914927c7bac4ecd2351bdee0cd5b2b1c11150342] +sid: released (5.4.8-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19058 b/retired/CVE-2019-19058 new file mode 100644 index 00000000..4462f0ae --- /dev/null +++ b/retired/CVE-2019-19058 @@ -0,0 +1,14 @@ +Description: iwlwifi: dbg_ini: fix memory leak in alloc_sgtable +References: +Notes: + carnil> Introduced in 7e62a699aafb ("iwlwifi: mvm: use + carnil> dev_coredumpsg()") in 4.10-rc1. +Bugs: +upstream: released (5.4-rc4) [b4b814fec1a5a849383f7b3886b654a13abbda7d] +4.19-upstream-stable: released (4.19.97) [09044a4a142404799e519def0bbfcc98fa68c677] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.4.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19059 b/retired/CVE-2019-19059 new file mode 100644 index 00000000..7b002be4 --- /dev/null +++ b/retired/CVE-2019-19059 @@ -0,0 +1,14 @@ +Description: iwlwifi: pcie: fix memory leaks in iwl_pcie_ctxt_info_gen3_init +References: +Notes: + carnil> Fixes 2ee824026288 ("iwlwifi: pcie: support context information + carnil> for 22560 devices") in 4.19-rc1. +Bugs: +upstream: released (5.4-rc4) [0f4f199443faca715523b0659aa536251d8b978f] +4.19-upstream-stable: released (4.19.97) [6e41dd9731e13b0bdf2f57f84b9d25d009bd9f87] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.4.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19062 b/retired/CVE-2019-19062 new file mode 100644 index 00000000..c783a598 --- /dev/null +++ b/retired/CVE-2019-19062 @@ -0,0 +1,16 @@ +Description: crypto: user - fix memory leak in crypto_report +References: + https://github.com/torvalds/linux/commit/ffdde5932042600c6807d46c1550b28b0db6a3bc +Notes: + bwh> Introduced in 3.2 by commit a38f7907b926 "crypto: Add userspace + bwh> configuration API". + carnil> Fixed as well in 5.3.16 and 5.4.3. +Bugs: +upstream: released (5.5-rc1) [ffdde5932042600c6807d46c1550b28b0db6a3bc] +4.19-upstream-stable: released (4.19.89) [351a567ebf2482de4dd5e5bbd539f2175540b717] +4.9-upstream-stable: released (4.9.207) [f427e1fcf77416ed14a716416c0faf2f02a1e68b] +3.16-upstream-stable: released (3.16.79) [52373b487ee420c43e1d9d01b4b8c11bb6e9bdbf] +sid: released (5.4.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19065 b/retired/CVE-2019-19065 new file mode 100644 index 00000000..39a24ef0 --- /dev/null +++ b/retired/CVE-2019-19065 @@ -0,0 +1,14 @@ +Description: RDMA/hfi1: Prevent memory leak in sdma_init +References: +Notes: + bwh> Intrdocued in 4.12 by commit 5a52a7acf7e2 "IB/hfi1: NULL pointer + bwh> dereference when freeing rhashtable". +Bugs: +upstream: released (5.4-rc3) [34b3be18a04ecdc610aae4c48e5d1b799d8689f6] +4.19-upstream-stable: released (4.19.82) [962cff4f3f89acf54b6fb418e7ff386b720b0fd6] +4.9-upstream-stable: N/A "Vulnerability introduced later" +3.16-upstream-stable: N/A "Vulnerability introduced later" +sid: released (5.3.9-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerability introduced later" +3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/retired/CVE-2019-19066 b/retired/CVE-2019-19066 new file mode 100644 index 00000000..15223dab --- /dev/null +++ b/retired/CVE-2019-19066 @@ -0,0 +1,14 @@ +Description: scsi: bfa: release allocated memory in case of error +References: + https://github.com/torvalds/linux/commit/0e62395da2bd5166d7c9e14cbc7503b256a34cb0 +Notes: + bwh> Introduced in 2.6.37 by commit a36c61f9025b "[SCSI] bfa: cleanup driver". +Bugs: +upstream: released (5.5-rc1) [0e62395da2bd5166d7c9e14cbc7503b256a34cb0] +4.19-upstream-stable: released (4.19.96) [486f51201528126bec2c647fa9d4216fc4fda91b] +4.9-upstream-stable: released (4.9.210) [78cb846f4aea6e20fc942d7bb8930107d1c6e34f] +3.16-upstream-stable: released (3.16.79) [0669f62b66de87c6628edc6b5e7e7b317a4b8876] +sid: released (5.4.13-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19068 b/retired/CVE-2019-19068 new file mode 100644 index 00000000..3414d425 --- /dev/null +++ b/retired/CVE-2019-19068 @@ -0,0 +1,15 @@ +Description: rtl8xxxu: prevent leaking urb +References: + https://github.com/torvalds/linux/commit/a2cdd07488e666aa93a49a3fc9c9b1299e27ef3c +Notes: + bwh> Introduced in 4.4 by commit 26f1fad29ad9 "New driver: rtl8xxxu + bwh> (mac80211)". +Bugs: +upstream: released (5.5-rc1) [a2cdd07488e666aa93a49a3fc9c9b1299e27ef3c] +4.19-upstream-stable: released (4.19.96) [0e27512c5d0bc2c3d33c1e7f73a8983015c82b83] +4.9-upstream-stable: released (4.9.210) [2c00bebd0b959fe8bec6d4a1a07010394b8008e4] +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.4.13-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19071 b/retired/CVE-2019-19071 new file mode 100644 index 00000000..5d30f172 --- /dev/null +++ b/retired/CVE-2019-19071 @@ -0,0 +1,16 @@ +Description: rsi: release skb if rsi_prepare_beacon fails +References: + https://github.com/torvalds/linux/commit/d563131ef23cbc756026f839a82598c8445bc45f +Notes: + bwh> Introduced in 4.14 by commit d26a9559403c "rsi: add beacon changes for + bwh> AP mode". + carnil> Fixed as well in 5.3.16 and 5.4.3 already. +Bugs: +upstream: released (5.5-rc1) [d563131ef23cbc756026f839a82598c8445bc45f] +4.19-upstream-stable: released (4.19.89) [5da96cc31633a9076404621ebb89bbe78f2c8676] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.4.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19077 b/retired/CVE-2019-19077 new file mode 100644 index 00000000..b07d9467 --- /dev/null +++ b/retired/CVE-2019-19077 @@ -0,0 +1,14 @@ +Description: RDMA: Fix goto target to release the allocated memory +References: +Notes: + carnil> Introduced in 37cb11acf1f7 ("RDMA/bnxt_re: Add SRQ support for + carnil> Broadcom adapters") in 4.16-rc1. +Bugs: +upstream: released (5.4-rc1) [4a9d46a9fe14401f21df69cea97c62396d5fb053] +4.19-upstream-stable: released (4.19.97) [d203ff6a3059b7fc3a9b48048eaf5641ed7fda2c] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.4.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19078 b/retired/CVE-2019-19078 new file mode 100644 index 00000000..5bfb4f39 --- /dev/null +++ b/retired/CVE-2019-19078 @@ -0,0 +1,15 @@ +Description: ath10k: fix memory leak +References: + https://github.com/torvalds/linux/commit/b8d17e7d93d2beb89e4f34c59996376b8b544792 +Notes: + bwh> Introduced in 4.14 by commit 4db66499df91 "ath10k: add initial USB + bwh> support". +Bugs: +upstream: released (5.5-rc1) [b8d17e7d93d2beb89e4f34c59996376b8b544792] +4.19-upstream-stable: released (4.19.96) [aed1b68eadf22513ac1fbd389f591f91c8bdaaf5] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.4.13-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19079 b/retired/CVE-2019-19079 new file mode 100644 index 00000000..cecc7ecc --- /dev/null +++ b/retired/CVE-2019-19079 @@ -0,0 +1,14 @@ +Description: net: qrtr: fix memort leak in qrtr_tun_write_iter +References: +Notes: + bwh> Introduced in 4.18 by commit 28fb4e59a47d "net: qrtr: Expose tunneling + bwh> endpoint to user space". Driver is not enabled in any Debian config. +Bugs: +upstream: released (5.3) [a21b7f0cff1906a93a0130b74713b15a0b36481d] +4.19-upstream-stable: released (4.19.89) [754e3c0c31c96cf3a4a54ed2a8c63cca28109136] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19080 b/retired/CVE-2019-19080 new file mode 100644 index 00000000..d998eff5 --- /dev/null +++ b/retired/CVE-2019-19080 @@ -0,0 +1,14 @@ +Description: nfp: flower: prevent memory leak in nfp_flower_spawn_phy_reprs +References: +Notes: + bwh> Introduced in 4.18 by commit b94524529741 "nfp: flower: add per repr + bwh> private data for LAG offload". +Bugs: +upstream: released (5.4-rc1) [8572cea1461a006bce1d06c0c4b0575869125fa4] +4.19-upstream-stable: released (4.19.77) [5b6c791f494d5e770dfd015390386f321b9a94da] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19081 b/retired/CVE-2019-19081 new file mode 100644 index 00000000..c373879c --- /dev/null +++ b/retired/CVE-2019-19081 @@ -0,0 +1,14 @@ +Description: nfp: flower: fix memory leak in nfp_flower_spawn_vnic_reprs +References: +Notes: + bwh> Introduced in 4.18 by commit b94524529741 "nfp: flower: add per repr + bwh> private data for LAG offload". +Bugs: +upstream: released (5.4-rc1) [8ce39eb5a67aee25d9f05b40b673c95b23502e3e] +4.19-upstream-stable: released (4.19.79) [04e0c84f137dd07aa931c00db1a2ac80f3be4be5] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19227 b/retired/CVE-2019-19227 new file mode 100644 index 00000000..f1234be3 --- /dev/null +++ b/retired/CVE-2019-19227 @@ -0,0 +1,12 @@ +Description: appletalk: Fix potential NULL pointer dereference in unregister_snap_clien +References: +Notes: +Bugs: +upstream: released (5.1-rc3) [9804501fa1228048857910a6bf23e085aade37cc] +4.19-upstream-stable: released (4.19.89) [0977763a13fd87a7aebe376dc96385758de3aa9e] +4.9-upstream-stable: released (4.9.207) [540b341012ba9b8e2963be3241cea229d4e4804d] +3.16-upstream-stable: released (3.16.79) [1551894964c90588b285d3a4f7da516e0ee9025a] +sid: released (5.2.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19332 b/retired/CVE-2019-19332 new file mode 100644 index 00000000..f8473af2 --- /dev/null +++ b/retired/CVE-2019-19332 @@ -0,0 +1,15 @@ +Description: KVM: x86: fix out-of-bounds write in KVM_GET_EMULATED_CPUID +References: + https://lore.kernel.org/kvm/000000000000ea5ec20598d90e50@google.com/ + https://www.openwall.com/lists/oss-security/2019/12/16/1 +Notes: + carnil> Fixed as well in 5.4.3 and 5.3.16 already. +Bugs: +upstream: released (5.5-rc1) [433f4ba1904100da65a311033f17a9bf586b287e] +4.19-upstream-stable: released (4.19.89) [5119ffd480b644d8bc9af741cc8ef435a7ec5ff7] +4.9-upstream-stable: released (4.9.207) [8b587e3f1424fae01f9c7e78d8d294bcb71f6f41] +3.16-upstream-stable: released (3.16.79) [21377f88c2757c6ee3e28407fb1c44b4bdf7e6b2] +sid: released (5.4.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19523 b/retired/CVE-2019-19523 new file mode 100644 index 00000000..5426e822 --- /dev/null +++ b/retired/CVE-2019-19523 @@ -0,0 +1,13 @@ +Description: USB: adutux: fix use-after-free on disconnect +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.4-rc3) [44efc269db7929f6275a1fa927ef082e533ecde0] +4.19-upstream-stable: released (4.19.80) [316f51d7759735a5295301ab22a7c6231b49c24f] +4.9-upstream-stable: released (4.9.197) [aa1b499d5f706c67a0acbe184e0ec32e8c47489b] +3.16-upstream-stable: released (3.16.79) [22cbb8fb12b3b5101260915162ad2b0b56a9284d] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19524 b/retired/CVE-2019-19524 new file mode 100644 index 00000000..8a01253f --- /dev/null +++ b/retired/CVE-2019-19524 @@ -0,0 +1,13 @@ +Description: Input: ff-memless - kill timer in destroy() +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.4-rc8) [fa3a5a1880c91bb92594ad42dfe9eedad7996b86] +4.19-upstream-stable: released (4.19.85) [c02230815282a436366d3d0d6de6d2636dd71b74] +4.9-upstream-stable: released (4.9.203) [1ce4561d12a08be9de2f2ef8ace700e55fc4835c] +3.16-upstream-stable: released (3.16.79) [8145f2181955c7c95f42a7f71b81ff91bc9e7b8c] +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19525 b/retired/CVE-2019-19525 new file mode 100644 index 00000000..8c1b5e18 --- /dev/null +++ b/retired/CVE-2019-19525 @@ -0,0 +1,13 @@ +Description: ieee802154: atusb: fix use-after-free at disconnect +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.4-rc2) [7fd25e6fc035f4b04b75bca6d7e8daa069603a76] +4.19-upstream-stable: released (4.19.79) [3f41e88f4bd44284c575ad3fb579581a16b39069] +4.9-upstream-stable: released (4.9.197) [2f2f3ffa761793f2db2f3b0bc6476a069061cb9c] +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19526 b/retired/CVE-2019-19526 new file mode 100644 index 00000000..c2c077a3 --- /dev/null +++ b/retired/CVE-2019-19526 @@ -0,0 +1,15 @@ +Description: NFC: pn533: fix use-after-free and memleaks +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: + bwh> Introduced in 4.12 by commit 32ecc75ded72 ("NFC: pn533: change order + bwh> operations in dev registation". +Bugs: +upstream: released (5.4-rc4) [6af3aa57a0984e061f61308fe181a9a12359fecc] +4.19-upstream-stable: released (4.19.82) [24aaf7f4528f0df0f29667d3921f4a63aa7b806c] +4.9-upstream-stable: N/A "Vulnerability introduced later" +3.16-upstream-stable: N/A "Vulnerability introduced later" +sid: released (5.3.9-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerability introduced later" +3.16-jessie-security: N/A "Vulnerability introduced later" diff --git a/retired/CVE-2019-19527 b/retired/CVE-2019-19527 new file mode 100644 index 00000000..ba8c6f11 --- /dev/null +++ b/retired/CVE-2019-19527 @@ -0,0 +1,14 @@ +Description: Use-after-free bug in drivers/hid/usbhid/hiddev.c driver +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: + carnil> Please double-check this triage/assessment. +Bugs: +upstream: released (5.3-rc4) [6d4472d7bec39917b54e4e80245784ea5d60ce49, 9c09b214f30e3c11f9b0b03f89442df03643794d] +4.19-upstream-stable: released (4.19.68) [b545dc9debe69ca513b93f4a244451e9be14b0c5, 0aab1a4653a6a21509e8add4bb460be76fcf9c70] +4.9-upstream-stable: released (4.9.190) [963a14fb9c43f0a6b38fbe3da0b894a147c71388, 52aaeae5f22247659238a06c36973775f57189f3] +3.16-upstream-stable: released (3.16.79) [a2133df2ca08f0d320e651f682f66a1097e6b752, daec20c79bdc41b44b651aa8c9506cb138a83952] +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19528 b/retired/CVE-2019-19528 new file mode 100644 index 00000000..393d582d --- /dev/null +++ b/retired/CVE-2019-19528 @@ -0,0 +1,16 @@ +Description: USB: iowarrior: fix use-after-free on disconnect +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: + carnil> The fix c468a8aa790e ("usb: iowarrior: fix deadlock on + carnil> disconnect") in 5.3-rc4 (and backported to 5.2.9, 4.19.67 and + carnil> 4.9.190) introduced the issue. +Bugs: +upstream: released (5.4-rc3) [edc4746f253d907d048de680a621e121517f484b] +4.19-upstream-stable: released (4.19.80) [2fdcf7e19bdefc683da824264c0898af39bf8d50] +4.9-upstream-stable: released (4.9.197) [323f425a7618fdb0b961dec2c58685fa32eafa1b] +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code not yet present in released version" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19529 b/retired/CVE-2019-19529 new file mode 100644 index 00000000..8f9b9ba7 --- /dev/null +++ b/retired/CVE-2019-19529 @@ -0,0 +1,15 @@ +Description: can: mcba_usb: fix use-after-free on disconnect +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: + bwh> Introduced in 4.12 by commit 51f3baad7de9 "can: mcba_usb: Add support + bwh> for Microchip CAN BUS Analyzer". +Bugs: +upstream: released (5.4-rc7) [4d6636498c41891d0482a914dd570343a838ad79] +4.19-upstream-stable: released (4.19.84) [ce9b94da0e043b7b0ec1bd3d0e451d956acff9c1] +4.9-upstream-stable: N/A "Vulnerable code not present" +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerable code not present" +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19530 b/retired/CVE-2019-19530 new file mode 100644 index 00000000..3ca3c9c9 --- /dev/null +++ b/retired/CVE-2019-19530 @@ -0,0 +1,13 @@ +Description: usb: cdc-acm: make sure a refcount is taken early enough +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.3-rc5) [c52873e5a1ef72f845526d9f6a50704433f9c625] +4.19-upstream-stable: released (4.19.68) [c02c0249ce5523a7a264136ed36f857b85555bac] +4.9-upstream-stable: released (4.9.190) [fccd6134d5addf2be1407e3250efdc854b5c5d8a] +3.16-upstream-stable: released (3.16.78) [3a8f54a68c9868ddae64603f2ddee082c1737075] +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19531 b/retired/CVE-2019-19531 new file mode 100644 index 00000000..769c5491 --- /dev/null +++ b/retired/CVE-2019-19531 @@ -0,0 +1,13 @@ +Description: usb: yurex: Fix use-after-free in yurex_delete +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.3-rc4) [fc05481b2fcabaaeccf63e32ac1baab54e5b6963] +4.19-upstream-stable: released (4.19.67) [33f2240acfa8b4017ee5dd64601c8a5ec7f53b4e] +4.9-upstream-stable: released (4.9.190) [e253114f73134cf6f29b453176fb537441e12371] +3.16-upstream-stable: released (3.16.78) [8f6204f2adba5354b65bd0f37b8d930e49df6420] +sid: released (5.2.9-1) +4.19-buster-security: released (4.19.67-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19532 b/retired/CVE-2019-19532 new file mode 100644 index 00000000..0ec2009b --- /dev/null +++ b/retired/CVE-2019-19532 @@ -0,0 +1,13 @@ +Description: HID: Fix assumption that devices have inputs +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.4-rc6) [d9d4b1e46d9543a82c23f6df03f4ad697dab361b] +4.19-upstream-stable: released (4.19.82) [8a01c4b908cf0a5367d3309c1c0d4e9be655ce00] +4.9-upstream-stable: released (4.9.199) [7b5e3ad5d582e252d971ee599a3f63f30b70ccb1] +3.16-upstream-stable: released (3.16.79) [f703c175f8e428959a33cdadb3e09986f14390ce] +sid: released (5.3.9-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19533 b/retired/CVE-2019-19533 new file mode 100644 index 00000000..db5e9320 --- /dev/null +++ b/retired/CVE-2019-19533 @@ -0,0 +1,13 @@ +Description: media: ttusb-dec: Fix info-leak in ttusb_dec_send_command() +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.4-rc1) [a10feaf8c464c3f9cfdd3a8a7ce17e1c0d498da1] +4.19-upstream-stable: released (4.19.77) [8630a4d13683095fbf14091d59a20e1ac71fdd6b] +4.9-upstream-stable: released (4.9.195) [70d5b96a1ed385a0ef520a44a18fbf6d795f1b84] +3.16-upstream-stable: released (3.16.79) [89577bea6adf8cd2a1b97c91f7266bb56aa181b0] +sid: released (5.3.7-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19534 b/retired/CVE-2019-19534 new file mode 100644 index 00000000..ff7da283 --- /dev/null +++ b/retired/CVE-2019-19534 @@ -0,0 +1,13 @@ +Description: can: peak_usb: fix slab info leak +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.4-rc7) [f7a1337f0d29b98733c8824e165fca3371d7d4fd] +4.19-upstream-stable: released (4.19.84) [a7be2debb769092c7c07b9a866b055d8bee5afaf] +4.9-upstream-stable: released (4.9.201) [da281558d20bfbf82823cab457ba7d343ba6b0a0] +3.16-upstream-stable: released (3.16.79) [f13615187cd8069c0f1c492e8f244a0c69d0663e] +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19535 b/retired/CVE-2019-19535 new file mode 100644 index 00000000..b1234f8f --- /dev/null +++ b/retired/CVE-2019-19535 @@ -0,0 +1,15 @@ +Description: can: peak_usb: pcan_usb_fd: Fix info-leaks to USB devices +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: + bwh> Introduced in 4.0 by commit 0a25e1f4f185 "can: peak_usb: add support + bwh> for PEAK new CANFD USB adapters". +Bugs: +upstream: released (5.3-rc4) [30a8beeb3042f49d0537b7050fd21b490166a3d9] +4.19-upstream-stable: released (4.19.67) [9ce1b3eb5489416338b2fb2b40f30f0d425700b4] +4.9-upstream-stable: released (4.9.190) [127ab64c38e21c55adf8781ca92f7dc9d1a9903e] +3.16-upstream-stable: N/A "Vulnerable code not present" +sid: released (5.2.9-1) +4.19-buster-security: released (4.19.67-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: N/A "Vulnerable code not present" diff --git a/retired/CVE-2019-19536 b/retired/CVE-2019-19536 new file mode 100644 index 00000000..51287c7b --- /dev/null +++ b/retired/CVE-2019-19536 @@ -0,0 +1,13 @@ +Description: can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.3-rc4) [ead16e53c2f0ed946d82d4037c630e2f60f4ab69] +4.19-upstream-stable: released (4.19.67) [cab569a44a524709d95bbd88700860ac45e5d5cf] +4.9-upstream-stable: released (4.9.190) [0cad79bfb5aa596b9449fe66b0edf69a8344326c] +3.16-upstream-stable: released (3.16.78) [06d7546f7b115a266a9bb81887479f38e166964e] +sid: released (5.2.9-1) +4.19-buster-security: released (4.19.67-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19537 b/retired/CVE-2019-19537 new file mode 100644 index 00000000..3d583de4 --- /dev/null +++ b/retired/CVE-2019-19537 @@ -0,0 +1,13 @@ +Description: USB: core: Fix races in character device registration and deregistraion +References: + http://www.openwall.com/lists/oss-security/2019/12/03/4 +Notes: +Bugs: +upstream: released (5.3-rc5) [303911cfc5b95d33687d9046133ff184cf5043ff] +4.19-upstream-stable: released (4.19.68) [7f52d6d2a82df15d7ea01d69d0943d2abc201b43] +4.9-upstream-stable: released (4.9.190) [741b832658b98463d619fe4c320f8ab11b2ad4ee] +3.16-upstream-stable: released (3.16.78) [7e0af4e53ee2cf9b5e4ee761bd8dc4f25a9c885a] +sid: released (5.2.17-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19767 b/retired/CVE-2019-19767 new file mode 100644 index 00000000..a8d31a7d --- /dev/null +++ b/retired/CVE-2019-19767 @@ -0,0 +1,16 @@ +Description: ext4: add more paranoia checking in ext4_expand_extra_isize handling +References: + https://bugzilla.kernel.org/show_bug.cgi?id=205609 + https://bugzilla.kernel.org/show_bug.cgi?id=205707 +Notes: + bwh> Apparently introduced in 2.6.23 by commit 6dd4ee7cab7e "ext4: + bwh> Expand extra_inodes space per the s_{want,min}_extra_isize fields". +Bugs: +upstream: released (5.5-rc1) [4ea99936a1630f51fc3a2d61a58ec4a1c4b7d55a] +4.19-upstream-stable: released (4.19.88) [e91cce02f3025da559468729ea0ad9dea242d3eb] +4.9-upstream-stable: released (4.9.211) [8e508ac2e7278759259fd818603af02e8e3a64f6] +3.16-upstream-stable: released (3.16.81) [f01bb82f5cde15ba2f6fc17cf706196a32aecd45] +sid: released (5.3.15-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) [bugfix/all/ext4-add-more-paranoia-checking-in-ext4_expand_extra_isize-handling.patch] +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19922 b/retired/CVE-2019-19922 new file mode 100644 index 00000000..cfe4f6e3 --- /dev/null +++ b/retired/CVE-2019-19922 @@ -0,0 +1,18 @@ +Description: sched/fair: Fix low cpu usage with high throttling by removing expiration of cpu-local slices +References: + https://github.com/kubernetes/kubernetes/issues/67577 + https://relistan.com/the-kernel-may-be-slowing-down-your-app + https://bugzilla.kernel.org/show_bug.cgi?id=198197 +Notes: + bwh> Apparently introduced in 4.18 by commit 512ac999d275 "sched/fair: + bwh> Fix bandwidth timer clock drift condition", which was backported to + bwh> 3.16 and 4.14. +Bugs: +upstream: released (5.4-rc1) [de53fd7aedb100f03e5d2231cfce0e4993282425] +4.19-upstream-stable: released (4.19.84) [502bd151448c2c76a927b26783e5538875c534ff] +4.9-upstream-stable: N/A "Vulnerability introduced later" +3.16-upstream-stable: released (3.16.81) [61749beefb4a12af7d91424bcd58ffdc072dad63] +sid: released (5.3.9-1) +4.19-buster-security: released (4.19.87-1) +4.9-stretch-security: N/A "Vulnerability introduced later" +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-19965 b/retired/CVE-2019-19965 new file mode 100644 index 00000000..e9162fed --- /dev/null +++ b/retired/CVE-2019-19965 @@ -0,0 +1,15 @@ +Description: scsi: libsas: stop discovering if oob mode is disconnected +References: +Notes: + carnil> Fixed as well in 5.4.9. + bwh> Apparently introduced in 2.6.19 by commit 2908d778ab3e "[SCSI] + bwh> aic94xx: new driver" before the function was moved into libsas. +Bugs: +upstream: released (5.5-rc2) [f70267f379b5e5e11bdc5d72a56bf17e5feed01f] +4.19-upstream-stable: released (4.19.94) [8b9bf467061bc89ccf4a43be637e08d8a70fd76d] +4.9-upstream-stable: released (4.9.209) [8febe765539fbcc7d47e4e2ad44a0bcb2adbf02b] +3.16-upstream-stable: released (3.16.81) [f4e74a1371c84cca35e53afda50759e2d44e0507] +sid: released (5.4.13-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) diff --git a/retired/CVE-2019-20096 b/retired/CVE-2019-20096 new file mode 100644 index 00000000..a01ae573 --- /dev/null +++ b/retired/CVE-2019-20096 @@ -0,0 +1,12 @@ +Description: dccp: Fix memleak in __feat_register_sp +References: +Notes: +Bugs: +upstream: released (5.1-rc4) [1d3ff0950e2b40dc861b1739029649d03f591820] +4.19-upstream-stable: released (4.19.97) [e58c590c772eb5dc5a3603c5aef4148f47ab2e20] +4.9-upstream-stable: released (4.9.211) [33cab7a0a84d35908c75c4b46c88769be7902556] +3.16-upstream-stable: released (3.16.72) [6f5a5f7e229e3ec71d729f3fd4479a11a0a21fd8] +sid: released (5.2.6-1) +4.19-buster-security: released (4.19.98-1) +4.9-stretch-security: released (4.9.210-1) [bugfix/all/dccp-fix-memleak-in-__feat_register_sp.patch] +3.16-jessie-security: released (3.16.72-1) diff --git a/retired/CVE-2019-2215 b/retired/CVE-2019-2215 new file mode 100644 index 00000000..91b06fa8 --- /dev/null +++ b/retired/CVE-2019-2215 @@ -0,0 +1,15 @@ +Description: Use-After-Free in Binder driver +References: + https://bugs.chromium.org/p/project-zero/issues/detail?id=1942 + https://googleprojectzero.blogspot.com/2019/11/bad-binder-android-in-wild-exploit.html +Notes: + bwh> Although the fix commit is marked "# 4.14", the bug is much older. +Bugs: +upstream: released (4.16-rc1) [f5cb779ba16334b45ba8946d6bfa6d9834d1527f] +4.19-upstream-stable: N/A "Fixed before branching point" +4.9-upstream-stable: released (4.9.196) [a494a71146a1cf3f48bb94cf33981db1f027e6a0] +3.16-upstream-stable: released (3.16.79) [3a593dd8bd7505f9acbc7b6f8928ec6b7978c125] +sid: released (4.15.4-1) +4.19-buster-security: N/A "Fixed before branching point" +4.9-stretch-security: released (4.9.210-1) +3.16-jessie-security: released (3.16.81-1) -- cgit v1.2.3