cve-extra-exclusions: remove historic kernel CVEs which are handled now
PATCH 1/2 cve-extra-exclusions: remove historic kernel CVEs which are handled now
From: Ross Burton <[email protected]>
The bulk of the historic kernel CVEs in this file are now handled by the include files generated by linux/generate-cve-exclusions.py, so remove them.
Those that remain date from 2017 or earlier, so rename the group to 'historic' and update the comment.
Signed-off-by Ross Burton <[email protected]>
--- .../distro/include/cve-extra-exclusions.inc | 47 ++++--------------- 1 file changed, 9 insertions(+), 38 deletions(-)
meta/conf/distro/include/cve-extra-exclusions.inc +9 -38
@@ -60,47 +60,18 @@ replacing bdb with supported and open source friendly alternatives. As a result # ensure the bulk of the major kernel CVEs are fixed and we don't dive into each individual issue # as the stable maintainers are much more able to do that. # -# Rather than just ignore all kernel CVEs, list the ones we ignore on this basis here, allowing new -# issues to be visible. If anyone wishes to clean up CPE entries with NIST for these, we'd -# welcome than and then entries can likely be removed from here. +# We have a script (generate-cve-exclusions.py) to have correct CVE status for backported issues, +# but the data on linuxkernelcves.com isn't 100% complete for the older CVEs. These historical +# CVEs need review and typically linuxkernelcves.com updated and then removed from here. # -CVE_STATUS_GROUPS += "CVE_STATUS_KERNEL_2010 CVE_STATUS_KERNEL_2017 CVE_STATUS_KERNEL_2018 CVE_STATUS_KERNEL_2020 \ - CVE_STATUS_KERNEL_2021 CVE_STATUS_KERNEL_2022" +CVE_STATUS_GROUPS += "CVE_STATUS_KERNEL_HISTORIC" -# 1999-2010 -CVE_STATUS_KERNEL_2010 = "CVE-1999-0524 CVE-1999-0656 CVE-2006-2932 CVE-2007-2764 CVE-2007-4998 CVE-2008-2544 \ - CVE-2008-4609 CVE-2010-0298 CVE-2010-4563" -CVE_STATUS_KERNEL_2010[status] = "ignored" - -# 2011-2017 -CVE_STATUS_KERNEL_2017 = "CVE-2011-0640 CVE-2014-2648 CVE-2014-8171 CVE-2016-0774 CVE-2016-3695 CVE-2016-3699 \ - CVE-2017-1000255 CVE-2017-1000377 CVE-2017-5897 CVE-2017-6264" -CVE_STATUS_KERNEL_2017[status] = "ignored" - -# 2018 -CVE_STATUS_KERNEL_2018 = "CVE-2018-1000026 CVE-2018-10840 CVE-2018-10876 CVE-2018-10882 CVE-2018-10901 CVE-2018-10902 \ - CVE-2018-14625 CVE-2018-16880 CVE-2018-16884 CVE-2018-5873" -CVE_STATUS_KERNEL_2018[status] = "ignored" - -# 2020 -CVE_STATUS_KERNEL_2020 = "CVE-2020-10732 CVE-2020-10742 CVE-2020-16119 CVE-2020-1749 CVE-2020-25672 CVE-2020-27820 CVE-2020-35501 CVE-2020-8834" -CVE_STATUS_KERNEL_2020[status] = "ignored" - -# 2021 -CVE_STATUS_KERNEL_2021 = "CVE-2021-20194 CVE-2021-20226 CVE-2021-20265 CVE-2021-3564 CVE-2021-3743 CVE-2021-3847 CVE-2021-4002 \ - CVE-2021-4090 CVE-2021-4095 CVE-2021-4197 CVE-2021-4202 CVE-2021-44879 CVE-2021-45402" -CVE_STATUS_KERNEL_2021[status] = "ignored" - -# 2022 -CVE_STATUS_KERNEL_2022 = "CVE-2022-0185 CVE-2022-0264 CVE-2022-0286 CVE-2022-0330 CVE-2022-0382 CVE-2022-0433 CVE-2022-0435 \ - CVE-2022-0492 CVE-2022-0494 CVE-2022-0500 CVE-2022-0516 CVE-2022-0617 CVE-2022-0742 CVE-2022-0854 \ - CVE-2022-0995 CVE-2022-0998 CVE-2022-1011 CVE-2022-1015 CVE-2022-1048 CVE-2022-1055 CVE-2022-1195 \ - CVE-2022-1353 CVE-2022-24122 CVE-2022-24448 CVE-2022-24958 CVE-2022-24959 CVE-2022-25258 CVE-2022-25265 \ - CVE-2022-25375 CVE-2022-26490 CVE-2022-26878 CVE-2022-26966 CVE-2022-27223 CVE-2022-27666 CVE-2022-27950 \ - CVE-2022-28356 CVE-2022-28388 CVE-2022-28389 CVE-2022-28390 CVE-2022-28796 CVE-2022-28893 CVE-2022-29156 \ - CVE-2022-29582 CVE-2022-29968" -CVE_STATUS_KERNEL_2022[status] = "ignored" +CVE_STATUS_KERNEL_HISTORIC = "CVE-1999-0524 CVE-1999-0656 CVE-2006-2932 CVE-2007-2764 CVE-2007-4998 \ + CVE-2008-2544 CVE-2008-4609 CVE-2010-0298 CVE-2010-4563 CVE-2011-0640 \ + CVE-2014-2648 CVE-2016-0774 CVE-2016-3695 CVE-2016-3699 CVE-2017-1000377 \ + CVE-2017-6264" +CVE_STATUS_KERNEL_HISTORIC[status] = "ignored" # https://nvd.nist.gov/vuln/detail/CVE-2022-3563
Signature · 1 line
2.34.1
PATCH 2/2 cve-extra-exclusions: remove BlueZ issues
From: Ross Burton <[email protected]>
These BlueZ issues were mislabelled as Linux issues, but now that the CPE data is accurate this ignore can be removed.
Signed-off-by Ross Burton <[email protected]>
--- meta/conf/distro/include/cve-extra-exclusions.inc | 5 ----- 1 file changed, 5 deletions(-)
meta/conf/distro/include/cve-extra-exclusions.inc +0 -5
@@ -74,11 +74,6 @@ CVE_STATUS_KERNEL_HISTORIC = "CVE-1999-0524 CVE-1999-0656 CVE-2006-2932 CVE-2007 CVE_STATUS_KERNEL_HISTORIC[status] = "ignored" -# https://nvd.nist.gov/vuln/detail/CVE-2022-3563 -# https://nvd.nist.gov/vuln/detail/CVE-2022-3637 -CVE_STATUS[CVE-2022-3563] = "cpe-incorrect: This issue do not affect the kernel, patchs listed on CVE pages links to https://git.kernel.org/pub/scm/bluetooth/bluez.git" -CVE_STATUS[CVE-2022-3637] = "cpe-incorrect: This issue do not affect the kernel, patchs listed on CVE pages links to https://git.kernel.org/pub/scm/bluetooth/bluez.git" - # qemu:qemu-native:qemu-system-native https://nvd.nist.gov/vuln/detail/CVE-2021-20255 CVE_STATUS[CVE-2021-20255] = "upstream-wontfix: \ There was a proposed patch https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg06098.html \
Signature · 1 line
2.34.1