diff options
| author | Salvatore Bonaccorso <carnil@debian.org> | 2021-11-28 20:40:36 +0100 |
|---|---|---|
| committer | Salvatore Bonaccorso <carnil@debian.org> | 2021-11-28 20:45:19 +0100 |
| commit | a81bb27318ad48581ed5950387be7c1c2c469051 (patch) | |
| tree | 049f001e1238d17948ed340f804f4bd5115c3d59 /data/DLA/list | |
| parent | b3c4c631e78be8486cc929b078cf180fc7e61c5b (diff) | |
Track CVE-2021-33560 and CVE-2021-40528
This got complex as the initial CVE assignment got swapped later.
Following other distributions we now recitify the old tracking.
This now was really a unnecessary burden, in particular because the
upstream repository commit reference will not swap the CVE in the commit
message, which I would expect can cause some further confusions.
Thus keep as well the notes about the swapping.
Diffstat (limited to 'data/DLA/list')
| -rw-r--r-- | data/DLA/list | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/data/DLA/list b/data/DLA/list index 911d1fa04d..e65cfc93ef 100644 --- a/data/DLA/list +++ b/data/DLA/list @@ -428,7 +428,7 @@ {CVE-2020-26558 CVE-2021-0129} [stretch] - bluez 5.43-2+deb9u4 [25 Jun 2021] DLA-2691-1 libgcrypt20 - security update - {CVE-2021-33560} + {CVE-2021-40528} [stretch] - libgcrypt20 1.7.6-2+deb9u4 [22 Jun 2021] DLA-2690-1 linux-4.19 - security update {CVE-2020-24586 CVE-2020-24587 CVE-2020-24588 CVE-2020-25670 CVE-2020-25671 CVE-2020-25672 CVE-2020-26139 CVE-2020-26147 CVE-2020-26558 CVE-2020-29374 CVE-2021-0129 CVE-2021-23133 CVE-2021-23134 CVE-2021-28688 CVE-2021-28964 CVE-2021-28971 CVE-2021-28972 CVE-2021-29154 CVE-2021-29155 CVE-2021-29264 CVE-2021-29647 CVE-2021-29650 CVE-2021-31829 CVE-2021-31916 CVE-2021-32399 CVE-2021-33034 CVE-2021-3483 CVE-2021-3506 CVE-2021-3564 CVE-2021-3573 CVE-2021-38208} |