<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.yoctoproject.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Marta+Rybczynska</id>
	<title>Yocto Project - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.yoctoproject.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Marta+Rybczynska"/>
	<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/Special:Contributions/Marta_Rybczynska"/>
	<updated>2026-04-04T23:04:09Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.5</generator>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86035</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86035"/>
		<updated>2023-10-30T07:17:47Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add a link to the stats from the autobuilder&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* [https://autobuilder.yocto.io/pub/non-release/patchmetrics/ autobuilder daily runs]&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
Please add all additional information after a ; sign to allow scripting.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If you have additional information (like a link to a patch), add it to the record&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too (this will be automated too)&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed (this is already automated)&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
NOTE: the current marking is only done for the master branch, for demo purposes&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *; fix not merged upstream https://dev.gnupg.org/D556&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *; no fix upstream https://bugzilla.nasm.us/show_bug.cgi?id=3392814&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *; disputed&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *; patch available https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=77c225bdeb410cf60da804879ad41622f5f1aa44&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 * ; disputed, sent ignore&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 * ; not applicable as we don&#039;t built minizip&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell ====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *  fedora/RHEL specific, sent ignore https://lists.openembedded.org/g/openembedded-core/message/189696&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86034</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86034"/>
		<updated>2023-10-30T07:06:45Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add embargoes case&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
&lt;br /&gt;
Note: this page is undergoing migration to [https://docs.yoctoproject.org/ the official Yocto Project documentation].&lt;br /&gt;
&lt;br /&gt;
== How to Report a Potential Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
If you would like to report a public issue (for example, one with a released CVE number), please report it using the [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla].&lt;br /&gt;
&lt;br /&gt;
If you are dealing with a not-yet-released or urgent issue, please send a message to security AT yoctoproject DOT org, including as many details as possible: the layer or software module affected, the recipe and its version, and any example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them for significant issues.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source software built or used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at the Yocto Project as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and would usually report the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels including a nomination deadline. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly. The aim is to have people representing technical leadership, security knowledge and infrastructure present with enough people to provide backup/coverage but keep the notification list small enough to minimise information risk and maintain trust.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Security Team Operations ==&lt;br /&gt;
&lt;br /&gt;
The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.&lt;br /&gt;
&lt;br /&gt;
Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team. &lt;br /&gt;
&lt;br /&gt;
The YP security team organizes its meetings and communication as needed.&lt;br /&gt;
&lt;br /&gt;
When the YP Security team receives a report about a potential security vulnerability, they quickly analyze and notify the reporter of the result. They might also request more information.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects the code maintained by the YP, they confidentially notify maintainers of that code and work with them to prepare a fix.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects an upstream project, the YP security team notifies the project. Usually, the upstream project analyzes the problem again. If they deem it a real security problem in their software, they develop and release a fix following their security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are generally non-public. The YP Security Team participates in the discussion as needed. They might also include the YP maintainer of the affected package.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
When the fix is publicly available, the YP security team member or the package maintainer sends patches against the YP code base, following usual procedures, including public code review.&lt;br /&gt;
&lt;br /&gt;
== Handling multi-project embargoes ==&lt;br /&gt;
&lt;br /&gt;
In rare cases, a severe security issue affects multiple projects. This might be numerous projects having a similar issue because of design, coding pattern, or reuse of the same code (an example of this situation is CVE-2023-44487 where multiple web servers share a design weakness). It might also be a high-profile issue in a commonly used library (like OpenSSL). In such cases, the project, learning first about the issue, might decide to notify other affected projects confidentially so that they come up with a synchronized fix. It might also be the affected project informing major distributions to roll out the update simultaneously.&lt;br /&gt;
&lt;br /&gt;
Such notifications happen over confidential, non-public means. Typically, the project initiating this &amp;quot;embargo&amp;quot; directly notifies a selected number of people from each project, including a subset of the security team. When Yocto Project is a part of such a notified group, developers prepare fixes on separate infrastructure and test it. They might also include additional developers and domain experts who can help with the fix and eventual regressions. When the embargo is lifted, they send a patch to the relevant public list, and the usual review process starts.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Marta Rybczynska &#039;&#039;&#039;&amp;lt;marta DOT rybczynska [at] syslinbit [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=marta.rybczynska@syslinbit.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Steve Sakoman &#039;&#039;&#039;&amp;lt;steve [at] sakoman [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=steve%40sakoman.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86033</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86033"/>
		<updated>2023-10-30T06:48:36Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add a note on migration to docs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
&lt;br /&gt;
Note: this page is undergoing migration to [https://docs.yoctoproject.org/ the official Yocto Project documentation].&lt;br /&gt;
&lt;br /&gt;
== How to Report a Potential Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
If you would like to report a public issue (for example, one with a released CVE number), please report it using the [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla].&lt;br /&gt;
&lt;br /&gt;
If you are dealing with a not-yet-released or urgent issue, please send a message to security AT yoctoproject DOT org, including as many details as possible: the layer or software module affected, the recipe and its version, and any example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them for significant issues.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source software built or used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at the Yocto Project as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and would usually report the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels including a nomination deadline. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly. The aim is to have people representing technical leadership, security knowledge and infrastructure present with enough people to provide backup/coverage but keep the notification list small enough to minimise information risk and maintain trust.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Security Team Operations ==&lt;br /&gt;
&lt;br /&gt;
The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.&lt;br /&gt;
&lt;br /&gt;
Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team. &lt;br /&gt;
&lt;br /&gt;
The YP security team organizes its meetings and communication as needed.&lt;br /&gt;
&lt;br /&gt;
When the YP Security team receives a report about a potential security vulnerability, they quickly analyze and notify the reporter of the result. They might also request more information.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects the code maintained by the YP, they confidentially notify maintainers of that code and work with them to prepare a fix.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects an upstream project, the YP security team notifies the project. Usually, the upstream project analyzes the problem again. If they deem it a real security problem in their software, they develop and release a fix following their security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are generally non-public. The YP Security Team participates in the discussion as needed. They might also include the YP maintainer of the affected package.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
When the fix is publicly available, the YP security team member or the package maintainer sends patches against the YP code base, following usual procedures, including public code review.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Marta Rybczynska &#039;&#039;&#039;&amp;lt;marta DOT rybczynska [at] syslinbit [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=marta.rybczynska@syslinbit.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Steve Sakoman &#039;&#039;&#039;&amp;lt;steve [at] sakoman [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=steve%40sakoman.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86030</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86030"/>
		<updated>2023-10-25T05:25:25Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* master */  Remove CVE-2023-3354&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
Please add all additional information after a ; sign to allow scripting.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If you have additional information (like a link to a patch), add it to the record&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too (this will be automated too)&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed (this is already automated)&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
NOTE: the current marking is only done for the master branch, for demo purposes&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *; fix not merged upstream https://dev.gnupg.org/D556&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *; no fix upstream https://bugzilla.nasm.us/show_bug.cgi?id=3392814&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *; disputed&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *; patch available https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=77c225bdeb410cf60da804879ad41622f5f1aa44&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 * ; disputed, sent ignore&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 * ; not applicable as we don&#039;t built minizip&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell ====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=SECURITY_file&amp;diff=86029</id>
		<title>SECURITY file</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=SECURITY_file&amp;diff=86029"/>
		<updated>2023-10-24T15:29:56Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add a note that the file is recommended to have&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= SECURITY.md file =&lt;br /&gt;
&lt;br /&gt;
SECURITY.md is a file where security researchers look into where they want to know how to report a potential security issue to a project confidentially. People who report security issues aren&#039;t necessarily developers. They might have limited knowledge of how the project functions and what are the customary communication methods.&lt;br /&gt;
&lt;br /&gt;
In addition to the way to contact the project team, it is also frequent to list releases that receive security fixes.&lt;br /&gt;
&lt;br /&gt;
Security researchers prefer confidential reporting and generally avoid posting them publicly -- if they can find a way to report confidentially. This increases the chances of preparing a fix before adversaries exploit the issue.&lt;br /&gt;
&lt;br /&gt;
The file might be straightforward and contain only essential information. Or, it might include links to other security materials, like documentation and policies. It is up to a layer maintainer to decide on the actual content.&lt;br /&gt;
&lt;br /&gt;
== Why to have a SECURITY.md? ==&lt;br /&gt;
&lt;br /&gt;
The first reason to have a SECURITY.md is to offer an easy way for security researchers to contact the project team in case of a potential security vulnerability. The file is the standard way to do it. Many software forges offer special formatting when they detect the file. See, for example, the OE GitHub mirror with the SECURITY.md listed automatically in the &#039;Security&#039; tab: https://github.com/openembedded/openembedded-core/security&lt;br /&gt;
&lt;br /&gt;
One might argue that Yocto Project layers contain only links to upstream sources, and all security issues should be reported to upstream projects. While it is valid for the first part, layers often include patches or apply configuration options. Such changes might create separate security issues. Finally, a confidential way to contact the project or layer is necessary to synchronize fixes between multiple distributions or downstream projects.&lt;br /&gt;
&lt;br /&gt;
The Yocto Project now strongly recommends all layers to have this file.&lt;br /&gt;
&lt;br /&gt;
== Generic SECURITY.md file ==&lt;br /&gt;
&lt;br /&gt;
The generic SECURITY.md file redirects to the Yocto Project Security Team. Here is an example taken from https://git.openembedded.org/openembedded-core/tree/SECURITY.md :&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;nowiki&amp;gt;&lt;br /&gt;
  How to Report a Potential Vulnerability?&lt;br /&gt;
  ========================================&lt;br /&gt;
&lt;br /&gt;
  If you would like to report a public issue (for example, one with a released&lt;br /&gt;
  CVE number), please report it using the&lt;br /&gt;
  [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla]&lt;br /&gt;
&lt;br /&gt;
  If you are dealing with a not-yet released or urgent issue, please send a&lt;br /&gt;
  message to security AT yoctoproject DOT org, including as many details as&lt;br /&gt;
  possible: the layer or software module affected, the recipe and its version,&lt;br /&gt;
  and any example code, if available.&lt;br /&gt;
&lt;br /&gt;
  Branches maintained with security fixes&lt;br /&gt;
  ---------------------------------------&lt;br /&gt;
&lt;br /&gt;
  See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]&lt;br /&gt;
  for detailed info regarding the policies and maintenance of Stable branches.&lt;br /&gt;
&lt;br /&gt;
  The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all&lt;br /&gt;
  releases of the Yocto Project. Versions in grey are no longer actively maintained with&lt;br /&gt;
  security patches, but well-tested patches may still be accepted for them for&lt;br /&gt;
  significant issues.&lt;br /&gt;
  &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Layer-specific SECURITY.md file ==&lt;br /&gt;
&lt;br /&gt;
A template asking to contact the maintainer. Adapt to your needs and processes:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;nowiki&amp;gt;&lt;br /&gt;
  How to Report a Potential Vulnerability?&lt;br /&gt;
  ========================================&lt;br /&gt;
&lt;br /&gt;
  If you would like to report a public issue (for example, one with a released&lt;br /&gt;
  CVE number), please get in touch with the layer maintainer:&lt;br /&gt;
  jane DOT doe AT example DOT org.&lt;br /&gt;
&lt;br /&gt;
  Branches maintained with security fixes&lt;br /&gt;
  ---------------------------------------&lt;br /&gt;
&lt;br /&gt;
  This project follows Yocto Project LTS policy. Please refer to the YP documentation&lt;br /&gt;
  for more details.&lt;br /&gt;
  &amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=SECURITY_file&amp;diff=86026</id>
		<title>SECURITY file</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=SECURITY_file&amp;diff=86026"/>
		<updated>2023-10-24T14:37:55Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add a page on SECURITY.md&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= SECURITY.md file =&lt;br /&gt;
&lt;br /&gt;
SECURITY.md is a file where security researchers look into where they want to know how to report a potential security issue to a project confidentially. People who report security issues aren&#039;t necessarily developers. They might have limited knowledge of how the project functions and what are the customary communication methods.&lt;br /&gt;
&lt;br /&gt;
In addition to the way to contact the project team, it is also frequent to list releases that receive security fixes.&lt;br /&gt;
&lt;br /&gt;
Security researchers prefer confidential reporting and generally avoid posting them publicly -- if they can find a way to report confidentially. This increases the chances of preparing a fix before adversaries exploit the issue.&lt;br /&gt;
&lt;br /&gt;
The file might be straightforward and contain only essential information. Or, it might include links to other security materials, like documentation and policies. It is up to a layer maintainer to decide on the actual content.&lt;br /&gt;
&lt;br /&gt;
== Why to have a SECURITY.md? ==&lt;br /&gt;
&lt;br /&gt;
The first reason to have a SECURITY.md is to offer an easy way for security researchers to contact the project team in case of a potential security vulnerability. The file is the standard way to do it. Many software forges offer special formatting when they detect the file. See, for example, the OE GitHub mirror with the SECURITY.md listed automatically in the &#039;Security&#039; tab: https://github.com/openembedded/openembedded-core/security&lt;br /&gt;
&lt;br /&gt;
One might argue that Yocto Project layers contain only links to upstream sources, and all security issues should be reported to upstream projects. While it is valid for the first part, layers often include patches or apply configuration options. Such changes might create separate security issues. Finally, a confidential way to contact the project or layer is necessary in case of a synchronization of fixes between multiple distributions or downstream projects.&lt;br /&gt;
&lt;br /&gt;
== Generic SECURITY.md file ==&lt;br /&gt;
&lt;br /&gt;
The generic SECURITY.md file redirects to the Yocto Project Security Team. Here is an example taken from https://git.openembedded.org/openembedded-core/tree/SECURITY.md :&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;nowiki&amp;gt;&lt;br /&gt;
  How to Report a Potential Vulnerability?&lt;br /&gt;
  ========================================&lt;br /&gt;
&lt;br /&gt;
  If you would like to report a public issue (for example, one with a released&lt;br /&gt;
  CVE number), please report it using the&lt;br /&gt;
  [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla]&lt;br /&gt;
&lt;br /&gt;
  If you are dealing with a not-yet released or urgent issue, please send a&lt;br /&gt;
  message to security AT yoctoproject DOT org, including as many details as&lt;br /&gt;
  possible: the layer or software module affected, the recipe and its version,&lt;br /&gt;
  and any example code, if available.&lt;br /&gt;
&lt;br /&gt;
  Branches maintained with security fixes&lt;br /&gt;
  ---------------------------------------&lt;br /&gt;
&lt;br /&gt;
  See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]&lt;br /&gt;
  for detailed info regarding the policies and maintenance of Stable branches.&lt;br /&gt;
&lt;br /&gt;
  The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all&lt;br /&gt;
  releases of the Yocto Project. Versions in grey are no longer actively maintained with&lt;br /&gt;
  security patches, but well-tested patches may still be accepted for them for&lt;br /&gt;
  significant issues.&lt;br /&gt;
  &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Layer-specific SECURITY.md file ==&lt;br /&gt;
&lt;br /&gt;
A template asking to contact the maintainer. Adapt to your needs and processes:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;nowiki&amp;gt;&lt;br /&gt;
  How to Report a Potential Vulnerability?&lt;br /&gt;
  ========================================&lt;br /&gt;
&lt;br /&gt;
  If you would like to report a public issue (for example, one with a released&lt;br /&gt;
  CVE number), please get in touch with the layer maintainer:&lt;br /&gt;
  jane DOT doe AT example DOT org.&lt;br /&gt;
&lt;br /&gt;
  Branches maintained with security fixes&lt;br /&gt;
  ---------------------------------------&lt;br /&gt;
&lt;br /&gt;
  This project follows Yocto Project LTS policy. Please refer to the YP documentation&lt;br /&gt;
  for more details.&lt;br /&gt;
  &amp;lt;/nowiki&amp;gt;&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security&amp;diff=86025</id>
		<title>Security</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security&amp;diff=86025"/>
		<updated>2023-10-24T14:10:57Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add a page on SECURITY.md&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Since the Yocto Project is intended to be flexible and meet the needs of many applications, we leave policy-making decisions around security to our end users. Our goal instead is to ship each release with metadata that follows best practices in that we try our best not to release recipe versions which are known to have significant security vulnerabilities. Generally this is done by upgrading recipes to newer versions that are no longer vulnerable to these issues. &lt;br /&gt;
&lt;br /&gt;
Upgrading recipes to the newer versions in the maintenance branches is not always easy, this is why we provide a patch for the existing version instead if we detect a vulnerability in a package. The patches are added to the recipes, see example below:&lt;br /&gt;
&lt;br /&gt;
  poky/recipes-connectivity/bind/bind_9.9.5.bb&lt;br /&gt;
  &lt;br /&gt;
  SRC_URI = &amp;quot;ftp://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.gz \&lt;br /&gt;
           file://conf.patch \&lt;br /&gt;
           ...&lt;br /&gt;
           file://bind9_9_5-CVE-2014-8500.patch \&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We provide a tool [https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/cve-check.bbclass cve-check.bbclass] to help report possible security vulnerabilities in the Yocto Project against the [http://nvd.nist.gov/home.cfm National Vulnerability Database]. Unpatched CVEs can be detected using the cve-checker which compares bitbake recipes, their versions and applied CVE patches to reported CVEs for that SW component name and version in the NVD database.&lt;br /&gt;
&lt;br /&gt;
Another good source to track reported CVEs is via the oss-security mailing list (Open Source Software Security) http://www.openwall.com/lists/oss-security/&lt;br /&gt;
&lt;br /&gt;
== Yocto Security Team ==&lt;br /&gt;
 &lt;br /&gt;
Currently, the Yocto Project DOES have a Security team.  We have two methods of communicating with the project. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Contact the Yocto Project regarding Security&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches. For more information including subscription information please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: For non-public or urgent issues.&lt;br /&gt;
&lt;br /&gt;
Anyone can contribute with security patches as before, but those volunteering to this security team will sync/organize security related activities and take more responsibility.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream projects analyzes the problem. If they deem that it is a real security problem in their software, the project will  email the linux-distros mailing list and notify all the big Linux distributions/vendors about the existence of this vulnerability/flaw. These mailing lists are normally non-public. The project and people on the linux-distros can then agree on a release date when the flaw should be made public.&lt;br /&gt;
There is also sometimes some coordination for handling patches or backporting of patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
When the security issue is finally to be made public, normally upstream project is responsible to contact Mitre (cve.mitre.org) to get a CVE number assigned to it and copy the information to other Opens Source Security mailing lists to inform the whole world of the vulnerability.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem the Yocto&#039;s Security Team will contact linux-distros and community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
Normally big Linux vendors fix the problem if the problem affects their products.&lt;br /&gt;
Chances are that everyone from the enterprise distros to the commercial Yocto vendors will get fixes done first, but it is nice to have safety net for issues that really are specific to OE and embedded.&lt;br /&gt;
&lt;br /&gt;
== Branches maintained with security fixes  ==&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance Stable branches maintenance]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.)&lt;br /&gt;
&lt;br /&gt;
== Policy for updating package versions for the stable branches ==&lt;br /&gt;
The Yocto project purposely limits updating of packages on oe-stable releases to items that address security problems (e.g. CVEs). For packages like QEMU we avoid updating between from one &amp;quot;dot.dot&amp;quot; to another related &amp;quot;dot.dot&amp;quot; version since it has been seen in the past that even with &amp;quot;simple&amp;quot; updates, things can go wrong and a lot more testing is required to verify compatibility. Better to only add CVE patches to fix specific point problems.&lt;br /&gt;
&lt;br /&gt;
== Kernel security patches ==&lt;br /&gt;
&lt;br /&gt;
Kernel security patches are backported to Linux-yocto kernels regularly from https://www.kernel.org/&lt;br /&gt;
=== Linux-yocto ===&lt;br /&gt;
linux-yocto_3 (maintainer: Bruce Ashfield)&lt;br /&gt;
&lt;br /&gt;
=== Vendor kernels ===&lt;br /&gt;
Kernel security patches are also backported to Linux-vendor kernels from https://www.kernel.org/&lt;br /&gt;
 &lt;br /&gt;
* meta-intel (meta-intel uses Linux-yocto)&lt;br /&gt;
* meta-xilinx (meta-xilinx@lists.yoctoproject.org)&lt;br /&gt;
* meta-ti (meta-ti@yoctoproject.org)&lt;br /&gt;
* etc&lt;br /&gt;
&lt;br /&gt;
== How to test ==&lt;br /&gt;
 &lt;br /&gt;
If there is any test case for the vulnerability by the upstream project or community&lt;br /&gt;
 - Run the test to reproduce the problem and verify the correction. &lt;br /&gt;
 - Run the regression test&lt;br /&gt;
&lt;br /&gt;
If there isn’t any test case and it is complicated and time consuming to write a testcase&lt;br /&gt;
 - Run the regression test&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Regression test&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* Build the core image for at least two architectures (preferably one big-endian and one little-endian)&lt;br /&gt;
* Run ptest (for those branches/packages that there is ptest mechanism)&lt;br /&gt;
&lt;br /&gt;
== Patch name convention and commit message ==&lt;br /&gt;
&lt;br /&gt;
Security patches like any Open Source development should follow the openembedded&#039;s Guidelines:&lt;br /&gt;
*[http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]&lt;br /&gt;
*[https://www.kernel.org/doc/Documentation/SecurityBugs kernel security bugs policy] &lt;br /&gt;
&lt;br /&gt;
Note that security patches should have CVE: tag and reference to the CVE identifier both in the patch file/s and the commit message.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Ex upstream patch:&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Please change the upstream patch &amp;quot;wscanf-allocates-too-little-memory.patch&amp;quot; to &amp;quot;CVE-2015-1472.patch&amp;quot; (or CVE-2015-1472-wscanf-allocates-too-little-memory.patch). Keep the original commit message and add reference to the CVE and upstream patch.&lt;br /&gt;
 &lt;br /&gt;
    &amp;lt;Keep the original commit message&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &lt;br /&gt;
    Upstream-Status: Accepted &amp;lt;or Backport&amp;gt;&lt;br /&gt;
    CVE: CVE-2015-8370   &lt;br /&gt;
    &lt;br /&gt;
    Reference to upstream patch:&lt;br /&gt;
    https://sourceware.org/git/?p=glibc.git;a=patch;h=5bd80bfe9ca0d955bfbbc002781bc7b01b6bcb06&lt;br /&gt;
      &lt;br /&gt;
    Signed-off-by: Joe Developer &amp;lt;joe.developer@example.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Ex meta patch:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Please make sure to add the package name in the subject and the reference to the CVE. Example for the commit message: &lt;br /&gt;
&lt;br /&gt;
    bash: CVE-2014-6278 &amp;lt;if there are multiple CVEs list all&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &amp;lt;short description&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &amp;lt;[YOCTO #xxx] if there is any&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    References&lt;br /&gt;
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6278&lt;br /&gt;
    https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-6278&lt;br /&gt;
    xxxx&lt;br /&gt;
    &lt;br /&gt;
    Signed-off-by: &amp;lt;your email address&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Workflow of Yocto Project&#039;s bugzilla ==&lt;br /&gt;
* To Open a Security defect go to [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security%20-%20Recipe%20Upgrade Security ‑ Recipe Upgrade]&lt;br /&gt;
** Access to this issue can only be viewed by the submitter and a small group of Bug triage folks:&lt;br /&gt;
*** Armin Kuster&lt;br /&gt;
*** Randy MacLeod&lt;br /&gt;
*** Richard Purdie&lt;br /&gt;
*** Ross Burton&lt;br /&gt;
*** Tim Orling&lt;br /&gt;
*** Stephen Jolley&lt;br /&gt;
** The normal bug triage process will be applied.&lt;br /&gt;
&lt;br /&gt;
* If the issue is already public please send the patch when available to the appropriate mailing list&lt;br /&gt;
* If the issue is private, attach a patch if available to the defect is preferred.&lt;br /&gt;
&lt;br /&gt;
== Some security related links/useful tools ==&lt;br /&gt;
&lt;br /&gt;
* [https://autobuilder.yocto.io/pub/non-release/patchmetrics/ Current CVE status for OE-Core/Poky] (generated by the Autobuilder)&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/images/5/58/Yocto_Summit_Lyon_Day1_2019.pdf#page=36 Yocto Project and CVEs, presentation by David Reyna in 2019 Yocto Developer day]&lt;br /&gt;
* [https://github.com/nluedtke/linux_kernel_cves/ Linux kernel fixed and reported CVEs in all branches and point releases]&lt;br /&gt;
** Note that cherry-picking CVE fixes for kernel is not recommended and users should merge full stable releases instead, see [http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/ What Stable Kernel Should I Use? by stable kernel maintainer Greg Kroah-Hartman]&lt;br /&gt;
* [http://www.cvedetails.com CVE details] &lt;br /&gt;
* [http://layers.openembedded.org/layerindex/branch/master/layer/meta-security/ Meta-security-layer]&lt;br /&gt;
* [https://docs.yoctoproject.org/dev-manual/common-tasks.html#making-images-more-secure Making Images More Secure] (Development Tasks Manual)&lt;br /&gt;
* [https://github.com/sjvermeu/cvechecker/ Cvechecker]&lt;br /&gt;
&lt;br /&gt;
== Security Issues Addressed in Yocto Releases ==&lt;br /&gt;
&lt;br /&gt;
== Current work in progress ==&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/Synchronization_CVEs Synchronization on the CVE work]&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/Security_private_reporting Security team and private reporting]&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/SECURITY_file SECURITY.md file]&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/File:Yocto_Project_Security_-_26_09_2023.pdf Related slides]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security&amp;diff=86024</id>
		<title>Security</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security&amp;diff=86024"/>
		<updated>2023-10-24T14:09:48Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: We have a security team now, update the information about the private mailing list.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Since the Yocto Project is intended to be flexible and meet the needs of many applications, we leave policy-making decisions around security to our end users. Our goal instead is to ship each release with metadata that follows best practices in that we try our best not to release recipe versions which are known to have significant security vulnerabilities. Generally this is done by upgrading recipes to newer versions that are no longer vulnerable to these issues. &lt;br /&gt;
&lt;br /&gt;
Upgrading recipes to the newer versions in the maintenance branches is not always easy, this is why we provide a patch for the existing version instead if we detect a vulnerability in a package. The patches are added to the recipes, see example below:&lt;br /&gt;
&lt;br /&gt;
  poky/recipes-connectivity/bind/bind_9.9.5.bb&lt;br /&gt;
  &lt;br /&gt;
  SRC_URI = &amp;quot;ftp://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.gz \&lt;br /&gt;
           file://conf.patch \&lt;br /&gt;
           ...&lt;br /&gt;
           file://bind9_9_5-CVE-2014-8500.patch \&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We provide a tool [https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/cve-check.bbclass cve-check.bbclass] to help report possible security vulnerabilities in the Yocto Project against the [http://nvd.nist.gov/home.cfm National Vulnerability Database]. Unpatched CVEs can be detected using the cve-checker which compares bitbake recipes, their versions and applied CVE patches to reported CVEs for that SW component name and version in the NVD database.&lt;br /&gt;
&lt;br /&gt;
Another good source to track reported CVEs is via the oss-security mailing list (Open Source Software Security) http://www.openwall.com/lists/oss-security/&lt;br /&gt;
&lt;br /&gt;
== Yocto Security Team ==&lt;br /&gt;
 &lt;br /&gt;
Currently, the Yocto Project DOES have a Security team.  We have two methods of communicating with the project. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Contact the Yocto Project regarding Security&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches. For more information including subscription information please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: For non-public or urgent issues.&lt;br /&gt;
&lt;br /&gt;
Anyone can contribute with security patches as before, but those volunteering to this security team will sync/organize security related activities and take more responsibility.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream projects analyzes the problem. If they deem that it is a real security problem in their software, the project will  email the linux-distros mailing list and notify all the big Linux distributions/vendors about the existence of this vulnerability/flaw. These mailing lists are normally non-public. The project and people on the linux-distros can then agree on a release date when the flaw should be made public.&lt;br /&gt;
There is also sometimes some coordination for handling patches or backporting of patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
When the security issue is finally to be made public, normally upstream project is responsible to contact Mitre (cve.mitre.org) to get a CVE number assigned to it and copy the information to other Opens Source Security mailing lists to inform the whole world of the vulnerability.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem the Yocto&#039;s Security Team will contact linux-distros and community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
Normally big Linux vendors fix the problem if the problem affects their products.&lt;br /&gt;
Chances are that everyone from the enterprise distros to the commercial Yocto vendors will get fixes done first, but it is nice to have safety net for issues that really are specific to OE and embedded.&lt;br /&gt;
&lt;br /&gt;
== Branches maintained with security fixes  ==&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance Stable branches maintenance]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.)&lt;br /&gt;
&lt;br /&gt;
== Policy for updating package versions for the stable branches ==&lt;br /&gt;
The Yocto project purposely limits updating of packages on oe-stable releases to items that address security problems (e.g. CVEs). For packages like QEMU we avoid updating between from one &amp;quot;dot.dot&amp;quot; to another related &amp;quot;dot.dot&amp;quot; version since it has been seen in the past that even with &amp;quot;simple&amp;quot; updates, things can go wrong and a lot more testing is required to verify compatibility. Better to only add CVE patches to fix specific point problems.&lt;br /&gt;
&lt;br /&gt;
== Kernel security patches ==&lt;br /&gt;
&lt;br /&gt;
Kernel security patches are backported to Linux-yocto kernels regularly from https://www.kernel.org/&lt;br /&gt;
=== Linux-yocto ===&lt;br /&gt;
linux-yocto_3 (maintainer: Bruce Ashfield)&lt;br /&gt;
&lt;br /&gt;
=== Vendor kernels ===&lt;br /&gt;
Kernel security patches are also backported to Linux-vendor kernels from https://www.kernel.org/&lt;br /&gt;
 &lt;br /&gt;
* meta-intel (meta-intel uses Linux-yocto)&lt;br /&gt;
* meta-xilinx (meta-xilinx@lists.yoctoproject.org)&lt;br /&gt;
* meta-ti (meta-ti@yoctoproject.org)&lt;br /&gt;
* etc&lt;br /&gt;
&lt;br /&gt;
== How to test ==&lt;br /&gt;
 &lt;br /&gt;
If there is any test case for the vulnerability by the upstream project or community&lt;br /&gt;
 - Run the test to reproduce the problem and verify the correction. &lt;br /&gt;
 - Run the regression test&lt;br /&gt;
&lt;br /&gt;
If there isn’t any test case and it is complicated and time consuming to write a testcase&lt;br /&gt;
 - Run the regression test&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Regression test&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* Build the core image for at least two architectures (preferably one big-endian and one little-endian)&lt;br /&gt;
* Run ptest (for those branches/packages that there is ptest mechanism)&lt;br /&gt;
&lt;br /&gt;
== Patch name convention and commit message ==&lt;br /&gt;
&lt;br /&gt;
Security patches like any Open Source development should follow the openembedded&#039;s Guidelines:&lt;br /&gt;
*[http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]&lt;br /&gt;
*[https://www.kernel.org/doc/Documentation/SecurityBugs kernel security bugs policy] &lt;br /&gt;
&lt;br /&gt;
Note that security patches should have CVE: tag and reference to the CVE identifier both in the patch file/s and the commit message.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Ex upstream patch:&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Please change the upstream patch &amp;quot;wscanf-allocates-too-little-memory.patch&amp;quot; to &amp;quot;CVE-2015-1472.patch&amp;quot; (or CVE-2015-1472-wscanf-allocates-too-little-memory.patch). Keep the original commit message and add reference to the CVE and upstream patch.&lt;br /&gt;
 &lt;br /&gt;
    &amp;lt;Keep the original commit message&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &lt;br /&gt;
    Upstream-Status: Accepted &amp;lt;or Backport&amp;gt;&lt;br /&gt;
    CVE: CVE-2015-8370   &lt;br /&gt;
    &lt;br /&gt;
    Reference to upstream patch:&lt;br /&gt;
    https://sourceware.org/git/?p=glibc.git;a=patch;h=5bd80bfe9ca0d955bfbbc002781bc7b01b6bcb06&lt;br /&gt;
      &lt;br /&gt;
    Signed-off-by: Joe Developer &amp;lt;joe.developer@example.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Ex meta patch:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Please make sure to add the package name in the subject and the reference to the CVE. Example for the commit message: &lt;br /&gt;
&lt;br /&gt;
    bash: CVE-2014-6278 &amp;lt;if there are multiple CVEs list all&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &amp;lt;short description&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &amp;lt;[YOCTO #xxx] if there is any&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    References&lt;br /&gt;
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6278&lt;br /&gt;
    https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-6278&lt;br /&gt;
    xxxx&lt;br /&gt;
    &lt;br /&gt;
    Signed-off-by: &amp;lt;your email address&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Workflow of Yocto Project&#039;s bugzilla ==&lt;br /&gt;
* To Open a Security defect go to [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security%20-%20Recipe%20Upgrade Security ‑ Recipe Upgrade]&lt;br /&gt;
** Access to this issue can only be viewed by the submitter and a small group of Bug triage folks:&lt;br /&gt;
*** Armin Kuster&lt;br /&gt;
*** Randy MacLeod&lt;br /&gt;
*** Richard Purdie&lt;br /&gt;
*** Ross Burton&lt;br /&gt;
*** Tim Orling&lt;br /&gt;
*** Stephen Jolley&lt;br /&gt;
** The normal bug triage process will be applied.&lt;br /&gt;
&lt;br /&gt;
* If the issue is already public please send the patch when available to the appropriate mailing list&lt;br /&gt;
* If the issue is private, attach a patch if available to the defect is preferred.&lt;br /&gt;
&lt;br /&gt;
== Some security related links/useful tools ==&lt;br /&gt;
&lt;br /&gt;
* [https://autobuilder.yocto.io/pub/non-release/patchmetrics/ Current CVE status for OE-Core/Poky] (generated by the Autobuilder)&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/images/5/58/Yocto_Summit_Lyon_Day1_2019.pdf#page=36 Yocto Project and CVEs, presentation by David Reyna in 2019 Yocto Developer day]&lt;br /&gt;
* [https://github.com/nluedtke/linux_kernel_cves/ Linux kernel fixed and reported CVEs in all branches and point releases]&lt;br /&gt;
** Note that cherry-picking CVE fixes for kernel is not recommended and users should merge full stable releases instead, see [http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/ What Stable Kernel Should I Use? by stable kernel maintainer Greg Kroah-Hartman]&lt;br /&gt;
* [http://www.cvedetails.com CVE details] &lt;br /&gt;
* [http://layers.openembedded.org/layerindex/branch/master/layer/meta-security/ Meta-security-layer]&lt;br /&gt;
* [https://docs.yoctoproject.org/dev-manual/common-tasks.html#making-images-more-secure Making Images More Secure] (Development Tasks Manual)&lt;br /&gt;
* [https://github.com/sjvermeu/cvechecker/ Cvechecker]&lt;br /&gt;
&lt;br /&gt;
== Security Issues Addressed in Yocto Releases ==&lt;br /&gt;
&lt;br /&gt;
== Current work in progress ==&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/Synchronization_CVEs Synchronization on the CVE work]&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/Security_private_reporting Security team and private reporting]&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/File:Yocto_Project_Security_-_26_09_2023.pdf Related slides]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86023</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86023"/>
		<updated>2023-10-24T08:08:22Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* master */ Re-add entries&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
Please add all additional information after a ; sign to allow scripting.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If you have additional information (like a link to a patch), add it to the record&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too (this will be automated too)&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed (this is already automated)&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
NOTE: the current marking is only done for the master branch, for demo purposes&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *; fix not merged upstream https://dev.gnupg.org/D556&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *; no fix upstream https://bugzilla.nasm.us/show_bug.cgi?id=3392814&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *; disputed&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *; patch available https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=77c225bdeb410cf60da804879ad41622f5f1aa44&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3354 (CVSS3: 7.5 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 * ; disputed, sent ignore&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 * ; not applicable as we don&#039;t built minizip&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell ====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86022</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86022"/>
		<updated>2023-10-24T08:07:10Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* master */ Update list (1 CVE removed)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
Please add all additional information after a ; sign to allow scripting.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If you have additional information (like a link to a patch), add it to the record&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too (this will be automated too)&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed (this is already automated)&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
NOTE: the current marking is only done for the master branch, for demo purposes&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *; fix not merged upstream https://dev.gnupg.org/D556&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *; no fix upstream https://bugzilla.nasm.us/show_bug.cgi?id=3392814&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *; disputed&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *; patch available https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=77c225bdeb410cf60da804879ad41622f5f1aa44&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3354 (CVSS3: 7.5 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 * ; disputed, sent ignore&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 * ; not applicable as we don&#039;t built minizip&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell ====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86020</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86020"/>
		<updated>2023-10-20T14:32:45Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* Current Security Team Members */ Add Steve and his key&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
&lt;br /&gt;
== How to Report a Potential Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
If you would like to report a public issue (for example, one with a released CVE number), please report it using the [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla].&lt;br /&gt;
&lt;br /&gt;
If you are dealing with a not-yet-released or urgent issue, please send a message to security AT yoctoproject DOT org, including as many details as possible: the layer or software module affected, the recipe and its version, and any example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them for significant issues.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source software built or used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at the Yocto Project as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and would usually report the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels including a nomination deadline. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly. The aim is to have people representing technical leadership, security knowledge and infrastructure present with enough people to provide backup/coverage but keep the notification list small enough to minimise information risk and maintain trust.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Security Team Operations ==&lt;br /&gt;
&lt;br /&gt;
The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.&lt;br /&gt;
&lt;br /&gt;
Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team. &lt;br /&gt;
&lt;br /&gt;
The YP security team organizes its meetings and communication as needed.&lt;br /&gt;
&lt;br /&gt;
When the YP Security team receives a report about a potential security vulnerability, they quickly analyze and notify the reporter of the result. They might also request more information.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects the code maintained by the YP, they confidentially notify maintainers of that code and work with them to prepare a fix.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects an upstream project, the YP security team notifies the project. Usually, the upstream project analyzes the problem again. If they deem it a real security problem in their software, they develop and release a fix following their security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are generally non-public. The YP Security Team participates in the discussion as needed. They might also include the YP maintainer of the affected package.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
When the fix is publicly available, the YP security team member or the package maintainer sends patches against the YP code base, following usual procedures, including public code review.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Marta Rybczynska &#039;&#039;&#039;&amp;lt;marta DOT rybczynska [at] syslinbit [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=marta.rybczynska@syslinbit.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Steve Sakoman &#039;&#039;&#039;&amp;lt;steve [at] sakoman [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=steve%40sakoman.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86019</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86019"/>
		<updated>2023-10-20T12:31:10Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Upate backpiort state&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: 1.17.x, need backport&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* lighthttpd&lt;br /&gt;
&lt;br /&gt;
Status: not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://redmine.lighttpd.net/boards/2/topics/11188&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: 1.47, need backport&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, need update to 20.8.1, patch pending https://lists.openembedded.org/g/openembedded-devel/message/105567&lt;br /&gt;
&lt;br /&gt;
Nanbield version: 20.5.1, need update to 20.8.1&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121 and https://github.com/nodejs/node/releases&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86018</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86018"/>
		<updated>2023-10-20T12:19:49Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update go status/kirkstone&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: 1.17.x, need backport&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* lighthttpd&lt;br /&gt;
&lt;br /&gt;
Status: not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://redmine.lighttpd.net/boards/2/topics/11188&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, need update to 20.8.1, patch pending https://lists.openembedded.org/g/openembedded-devel/message/105567&lt;br /&gt;
&lt;br /&gt;
Nanbield version: 20.5.1, need update to 20.8.1&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121 and https://github.com/nodejs/node/releases&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86017</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86017"/>
		<updated>2023-10-20T11:46:01Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update go status/kirkstone&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: 1.17.x, backport in progress&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* lighthttpd&lt;br /&gt;
&lt;br /&gt;
Status: not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://redmine.lighttpd.net/boards/2/topics/11188&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, need update to 20.8.1, patch pending https://lists.openembedded.org/g/openembedded-devel/message/105567&lt;br /&gt;
&lt;br /&gt;
Nanbield version: 20.5.1, need update to 20.8.1&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121 and https://github.com/nodejs/node/releases&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86016</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86016"/>
		<updated>2023-10-20T08:27:38Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* Synchronization page */  Clarify the procedure&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
Please add all additional information after a ; sign to allow scripting.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If you have additional information (like a link to a patch), add it to the record&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too (this will be automated too)&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed (this is already automated)&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
NOTE: the current marking is only done for the master branch, for demo purposes&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *; fix not merged upstream https://dev.gnupg.org/D556&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *; fix committed https://github.com/amstewart/libsndfile/commit/57ad7b69431073d52312a69addd46221029ccb08&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *; no fix upstream https://bugzilla.nasm.us/show_bug.cgi?id=3392814&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *; disputed&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *; patch available https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=77c225bdeb410cf60da804879ad41622f5f1aa44&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3354 (CVSS3: 7.5 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell ====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86015</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86015"/>
		<updated>2023-10-20T08:26:02Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* master */ Triaging of some pending CVEs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
NOTE: the current marking is only done for the master branch, for demo purposes&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *; fix not merged upstream https://dev.gnupg.org/D556&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *; fix committed https://github.com/amstewart/libsndfile/commit/57ad7b69431073d52312a69addd46221029ccb08&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *; no fix upstream https://bugzilla.nasm.us/show_bug.cgi?id=3392814&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *; disputed&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *; patch available https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=77c225bdeb410cf60da804879ad41622f5f1aa44&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3354 (CVSS3: 7.5 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell ====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86014</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86014"/>
		<updated>2023-10-20T08:05:16Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* dunfell = */ Fix typo&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
NOTE: the current marking is only done for the master branch, for demo purposes&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3354 (CVSS3: 7.5 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell ====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86013</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86013"/>
		<updated>2023-10-20T08:04:43Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* Current status */  Add a note for the status&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
NOTE: the current marking is only done for the master branch, for demo purposes&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3354 (CVSS3: 7.5 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell =====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86012</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86012"/>
		<updated>2023-10-20T08:03:31Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* Synchronization page */  Add procedure proposal&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
The proposed procedure:&lt;br /&gt;
* Mark name of a person preparing a patch for each branch&lt;br /&gt;
* If a patch is posted to the mailing list, post a link to it (this will be automated)&lt;br /&gt;
* When a patch reaches the &amp;quot;next&amp;quot; branch, mark it too&lt;br /&gt;
* When the patch reaches the final branch, the line of the CVE is automatically removed&lt;br /&gt;
* The list is (re)generated every day&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
=== Current status ===&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3354 (CVSS3: 7.5 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell =====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86011</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86011"/>
		<updated>2023-10-20T07:58:12Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add raw CVE data&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes. Please note your name/handle when you are working on preparing a fix for that issue.&lt;br /&gt;
&lt;br /&gt;
The list is auto-generated, and the format will change to fit the needs.&lt;br /&gt;
&lt;br /&gt;
An alternative to managing the effort would be to generate Bugzilla entries (not done at this point)&lt;br /&gt;
&lt;br /&gt;
==== Further work ====&lt;br /&gt;
&lt;br /&gt;
* Auto-update the page&lt;br /&gt;
* Auto-fill patches pending from the ML archive/patchwork&lt;br /&gt;
&lt;br /&gt;
==== master ====&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0687 (CVSS3: 9.8 CRITICAL): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0687 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3180 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3180 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3354 (CVSS3: 7.5 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3354 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38559 (CVSS3: 5.5 MEDIUM): ghostscript https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39928 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39928 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
==== mickledore ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-46456 (CVSS3: 6.1 MEDIUM): nasm:nasm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-46456 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2176 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2176 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25585 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25585 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25588 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25588 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38039 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39318 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39318 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39319 (CVSS3: 6.1 MEDIUM): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-binary-native:go-cross-core2-64:go-runtime https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40030 (CVSS3: 6.1 MEDIUM): rust:rust-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40030 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43804 (CVSS3: 8.1 HIGH): python3-urllib3 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43804 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-binary-native:go-cross-core2-64:go-runtime:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4504 (CVSS3: 7.8 HIGH): cups https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4504 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4911 (CVSS3: 7.8 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4911 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== kirkstone ====&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3114 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3114 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3964 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3964 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3965 (CVSS3: 8.1 HIGH): ffmpeg https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3965 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45888 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45888 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47940 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47940 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1872 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32247 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32250 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32250 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32252 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32252 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32254 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32254 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32257 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32257 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32258 (CVSS3: 8.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32258 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3389 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3439 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3439 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38427 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38427 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38430 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38431 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38431 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:nghttp2 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5197 (CVSS3: 6.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5197 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;br /&gt;
&lt;br /&gt;
==== dunfell =====&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0524 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0524 *&lt;br /&gt;
&lt;br /&gt;
CVE-1999-0656 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-1999-0656 *&lt;br /&gt;
&lt;br /&gt;
CVE-2006-2932 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2006-2932 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-2764 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-2764 *&lt;br /&gt;
&lt;br /&gt;
CVE-2007-4998 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2007-4998 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-2544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-2544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2008-4609 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2008-4609 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-0298 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0298 *&lt;br /&gt;
&lt;br /&gt;
CVE-2010-4563 (CVSS3: N/A): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-4563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-0774 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-0774 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3695 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2016-3699 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-3699 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-1000377 (CVSS3: 5.9 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000377 *&lt;br /&gt;
&lt;br /&gt;
CVE-2017-6264 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-6264 *&lt;br /&gt;
&lt;br /&gt;
CVE-2018-6559 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6559 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-14899 (CVSS3: 7.4 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-14899 *&lt;br /&gt;
&lt;br /&gt;
CVE-2019-20794 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20794 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11725 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11725 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-11935 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-11935 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-15705 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-15705 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-16120 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-16120 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25742 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25742 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-25743 (CVSS3: 3.2 LOW): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-25743 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-27918 (CVSS3: 7.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-27918 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29534 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-29623 (CVSS3: 3.3 LOW): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-29623 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35501 (CVSS3: 3.4 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35501 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35503 (CVSS3: 6.0 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35503 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-35506 (CVSS3: 6.7 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-35506 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36310 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36310 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36385 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36691 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36691 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-36766 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-36766 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9948 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9948 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9951 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9951 *&lt;br /&gt;
&lt;br /&gt;
CVE-2020-9952 (CVSS3: 7.1 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-9952 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1765 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1789 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1799 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1799 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1801 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1801 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-1870 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-1870 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20269 (CVSS3: 5.5 MEDIUM): kexec-tools https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20269 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-20295 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-20295 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-26934 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-26934 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27097 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27097 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-27138 (CVSS3: 7.8 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27138 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-29155 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-31879 (CVSS3: 6.1 MEDIUM): wget https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-31879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-32078 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32078 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3418 (CVSS3: 6.4 MEDIUM): grub:grub-efi:grub-efi-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3418 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3445 (CVSS3: 7.5 HIGH): libdnf https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3445 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35937 (CVSS3: 6.4 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35937 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35938 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-35939 (CVSS3: 6.7 MEDIUM): rpm:rpm-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-35939 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3611 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3669 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3669 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3714 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3714 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3773 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3782 (CVSS3: 6.6 MEDIUM): wayland:wayland-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3782 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3847 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3847 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3864 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3864 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-3947 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-3947 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4023 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4023 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4148 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4148 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4150 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4150 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-4218 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-4218 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-42762 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-42762 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-44879 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-44879 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45085 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45085 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45086 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45086 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45087 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45087 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45088 (CVSS3: 6.1 MEDIUM): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45088 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45481 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45481 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45482 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45482 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-45483 (CVSS3: 6.5 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-45483 *&lt;br /&gt;
&lt;br /&gt;
CVE-2021-46174 (CVSS3: 7.5 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-46174 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0168 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0168 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0358 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0382 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0382 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0400 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0400 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-0480 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-0480 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1247 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1247 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1263 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1263 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1508 (CVSS3: 6.1 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1508 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-1789 (CVSS3: 6.8 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2294 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2294 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2327 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2327 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2347 (CVSS3: 7.1 HIGH): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2347 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-23773 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-23773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-24765 (CVSS3: 7.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24765 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-25265 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25265 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-26878 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-26878 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2953 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2953 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-29536 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-29536 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2961 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2961 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2962 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2962 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-2991 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-2991 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30293 (CVSS3: 7.5 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30293 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-30767 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-30767 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3108 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3108 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3219 (CVSS3: 3.3 LOW): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3219 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-32893 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-32893 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-33065 (CVSS3: 7.8 HIGH): libsndfile1 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-33065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3344 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-34835 (CVSS3: 9.8 CRITICAL): u-boot https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34835 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3515 (CVSS3: 9.8 CRITICAL): gnupg:gnupg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3515 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3523 (CVSS3: 5.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3523 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3533 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3534 (CVSS3: 8.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3534 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3544 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3563 (CVSS3: 5.7 MEDIUM): bluez5 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3563 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3566 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3566 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3567 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3567 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3595 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3595 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3606 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3606 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3624 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3624 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3636 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36402 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36402 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-36648 (CVSS3: 10.0 CRITICAL): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-36648 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38096 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38096 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-38457 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-3872 (CVSS3: 8.6 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-3872 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39253 (CVSS3: 5.5 MEDIUM): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39253 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-39260 (CVSS3: 8.8 HIGH): git https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-39260 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40090 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40090 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-40897 (CVSS3: 5.9 MEDIUM): python3-setuptools:python3-setuptools-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-40897 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41720 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41720 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41724 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41724 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-41848 (CVSS3: 4.2 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-41848 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44032 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44032 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44033 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44033 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44034 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44034 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44617 (CVSS3: 7.5 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44617 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-44840 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-44840 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4543 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4543 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45703 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45703 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45884 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45884 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45885 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45885 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45886 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45886 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45887 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45887 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-45919 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-45919 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47007 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47008 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47008 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47010 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47011 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47011 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47520 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47520 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47673 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47673 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47695 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47695 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-47696 (CVSS3: 7.8 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-47696 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48063 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48063 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48064 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48064 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48065 (CVSS3: 5.5 MEDIUM): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48065 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-48554 (CVSS3: 5.5 MEDIUM): file:file-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48554 *&lt;br /&gt;
&lt;br /&gt;
CVE-2022-4883 (CVSS3: 8.8 HIGH): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-4883 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0160 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0160 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-0240 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-0240 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1075 (CVSS3: 3.3 LOW): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1075 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1206 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1249 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1249 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1281 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1281 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1386 (CVSS3: 7.8 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1386 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1544 (CVSS3: 6.3 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1544 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1582 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1582 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-1916 (CVSS3: 6.1 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-1916 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2007 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2007 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-22995 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22995 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23000 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23000 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23004 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23004 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-23039 (CVSS3: 5.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-23039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2430 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2430 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-24532 (CVSS3: 5.3 MEDIUM): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-24532 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25358 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25358 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25360 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25361 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25361 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25362 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25362 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25363 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25363 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-25584 (CVSS3: 7.1 HIGH): binutils:binutils-cross-testsuite:binutils-cross-x86_64:binutils-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-25584 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26081 (CVSS3: 7.5 HIGH): epiphany https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26081 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-26242 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26242 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2680 (CVSS3: 8.2 HIGH): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2680 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-27043 (CVSS3: 5.3 MEDIUM): python3:python3-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-27043 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-2731 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-2731 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28319 (CVSS3: 7.5 HIGH): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28319 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28321 (CVSS3: 5.9 MEDIUM): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28321 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28322 (CVSS3: 3.7 LOW): curl:curl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-28938 (CVSS3: 4.4 MEDIUM): mdadm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28938 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29403 (CVSS3: 7.8 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29403 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29491 (CVSS3: 7.8 HIGH): ncurses:ncurses-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29491 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-29499 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-29499 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3019 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3019 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31484 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31484 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-31486 (CVSS3: 8.1 HIGH): perl:perl-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-31486 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3255 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3255 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32611 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32636 (CVSS3: 7.5 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32636 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32643 (CVSS3: 7.8 HIGH): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32643 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-32665 (CVSS3: 5.5 MEDIUM): glib-2.0:glib-2.0-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32665 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3301 (CVSS3: 5.6 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3301 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-33288 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-33288 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3341 (CVSS3: 7.5 HIGH): bind https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3341 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3576 (CVSS3: 5.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3576 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-35827 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-35827 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3611 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3640 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3640 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37453 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37453 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37454 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37454 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3772 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3772 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3773 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3773 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-37769 (CVSS3: 6.5 MEDIUM): pixman:pixman-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-37769 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-3777 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3777 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38560 (CVSS3: 5.5 MEDIUM): ghostscript:ghostscript-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38560 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-38633 (CVSS3: 5.5 MEDIUM): librsvg:librsvg-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38633 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39191 (CVSS3: 8.2 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39191 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39193 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39193 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39194 (CVSS3: 4.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39323 (CVSS3: 9.8 CRITICAL): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39323 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-39533 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39533 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4010 (CVSS3: 4.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4010 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4015 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4015 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40283 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40283 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40360 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40360 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4039 (CVSS3: 4.8 MEDIUM): gcc:gcc-cross-x86_64:gcc-runtime:gcc-sanitizers:libgcc:libgcc-initial https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4039 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40397 (CVSS3: 9.8 CRITICAL): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40397 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40745 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40745 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-40791 (CVSS3: 9.1 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40791 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-41175 (CVSS3: 6.5 MEDIUM): tiff https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-41175 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4128 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4128 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4133 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4133 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4135 (CVSS3: 6.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4135 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4155 (CVSS3: 5.6 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4155 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4194 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4194 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4206 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4206 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4207 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4207 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4208 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4208 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4244 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4244 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42467 (CVSS3: 5.5 MEDIUM): qemu:qemu-native:qemu-system-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42467 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4273 (CVSS3: 6.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4273 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42752 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42752 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42753 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42753 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42754 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42754 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42755 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42755 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-42756 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-42756 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43785 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43785 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43786 (CVSS3: 5.5 MEDIUM): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43786 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43787 (CVSS3: 7.8 HIGH): libx11:libx11-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43787 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43788 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43788 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-43789 (CVSS3: 5.5 MEDIUM): libxpm https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-43789 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4385 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4385 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4387 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4387 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4389 (CVSS3: 7.1 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4389 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4394 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4394 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44466 (CVSS3: 8.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44466 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-44487 (CVSS3: 7.5 HIGH): go:go-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44487 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4459 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4459 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4527 (CVSS3: 6.5 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4527 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45322 (CVSS3: 6.5 MEDIUM): libxml2:libxml2-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45322 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4569 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4569 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45853 (CVSS3: 9.8 CRITICAL): zlib:zlib-native https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45853 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45862 (CVSS3: 7.5 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45862 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45863 (CVSS3: 6.4 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45871 (CVSS3: 9.8 CRITICAL): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45871 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-45898 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45898 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4611 (CVSS3: 6.3 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4611 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4622 (CVSS3: 7.0 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4622 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4732 (CVSS3: 4.7 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4732 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4813 (CVSS3: 5.9 MEDIUM): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4813 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4863 (CVSS3: 8.8 HIGH): libwebp https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-4921 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4921 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5156 (CVSS3: 7.5 HIGH): glibc https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5156 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5158 (CVSS3: 5.5 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5158 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5344 (CVSS3: 7.5 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5344 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5345 (CVSS3: 7.8 HIGH): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5345 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5441 (CVSS3: 5.5 MEDIUM): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5441 *&lt;br /&gt;
&lt;br /&gt;
CVE-2023-5535 (CVSS3: 7.8 HIGH): vim https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-5535 *&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86010</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86010"/>
		<updated>2023-10-20T07:24:37Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Fix formatting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
* weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
* autobuilder daily runs&lt;br /&gt;
* runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes.&lt;br /&gt;
&lt;br /&gt;
WIP&lt;br /&gt;
&lt;br /&gt;
To cover:&lt;br /&gt;
* Who updates the page?&lt;br /&gt;
* What happens when a fix is posted on the ML?&lt;br /&gt;
* How do we handle different LTS versions&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86009</id>
		<title>Synchronization CVEs</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Synchronization_CVEs&amp;diff=86009"/>
		<updated>2023-10-20T07:22:23Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* Regular cve-check runs */  Add cve-check runs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== (WIP) Synchronization on the CVE work ==&lt;br /&gt;
&lt;br /&gt;
The Yocto project is actively fixing public CVEs. This page describes the process to follow to allow synchronization between developers. The goal is to avoid duplicate work, and also limit the number of high severity CVEs that remain without a backport of the fix.&lt;br /&gt;
&lt;br /&gt;
=== Regular cve-check runs ===&lt;br /&gt;
&lt;br /&gt;
The project runs cve-check regularly on the Poky repository with a world build. This allows the generation of an up-to-date state of the known CVEs.&lt;br /&gt;
&lt;br /&gt;
Results from multiple runs of the cve-check are available:&lt;br /&gt;
&lt;br /&gt;
- weekly emails sent to the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list]&lt;br /&gt;
- autobuilder daily runs&lt;br /&gt;
- runs managed by Project&#039;s collaborators&lt;br /&gt;
&lt;br /&gt;
=== Synchronization page ===&lt;br /&gt;
&lt;br /&gt;
A synchronization wiki page is available for everyone working on CVE fixes.&lt;br /&gt;
&lt;br /&gt;
WIP&lt;br /&gt;
&lt;br /&gt;
To cover:&lt;br /&gt;
* Who updates the page?&lt;br /&gt;
* What happens when a fix is posted on the ML?&lt;br /&gt;
* How do we handle different LTS versions&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86008</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86008"/>
		<updated>2023-10-19T07:50:13Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add patch pending for nodejs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* lighthttpd&lt;br /&gt;
&lt;br /&gt;
Status: not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://redmine.lighttpd.net/boards/2/topics/11188&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, need update to 20.8.1, patch pending https://lists.openembedded.org/g/openembedded-devel/message/105567&lt;br /&gt;
&lt;br /&gt;
Nanbield version: 20.5.1, need update to 20.8.1&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121 and https://github.com/nodejs/node/releases&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86007</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86007"/>
		<updated>2023-10-19T07:25:57Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* meta-openembedded */ Update nodejs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* lighthttpd&lt;br /&gt;
&lt;br /&gt;
Status: not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://redmine.lighttpd.net/boards/2/topics/11188&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, need update to 20.8.1&lt;br /&gt;
&lt;br /&gt;
Nanbield version: 20.5.1, need update to 20.8.1&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121 and https://github.com/nodejs/node/releases&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86006</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=86006"/>
		<updated>2023-10-19T07:24:07Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: /* meta-openembedded */ Update nodejs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* lighthttpd&lt;br /&gt;
&lt;br /&gt;
Status: not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://redmine.lighttpd.net/boards/2/topics/11188&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, need update to 20.8.1&lt;br /&gt;
&lt;br /&gt;
Nanbield version: need update to 18.18.2&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121 and https://github.com/nodejs/node/releases&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86003</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86003"/>
		<updated>2023-10-18T05:29:15Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Fix formatting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
&lt;br /&gt;
== How to Report a Potential Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
If you would like to report a public issue (for example, one with a released CVE number), please report it using the [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla].&lt;br /&gt;
&lt;br /&gt;
If you are dealing with a not-yet-released or urgent issue, please send a message to security AT yoctoproject DOT org, including as many details as possible: the layer or software module affected, the recipe and its version, and any example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them for significant issues.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source software built or used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at the Yocto Project as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and would usually report the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels including a nomination deadline. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly. The aim is to have people representing technical leadership, security knowledge and infrastructure present with enough people to provide backup/coverage but keep the notification list small enough to minimise information risk and maintain trust.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Security Team Operations ==&lt;br /&gt;
&lt;br /&gt;
The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.&lt;br /&gt;
&lt;br /&gt;
Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team. &lt;br /&gt;
&lt;br /&gt;
The YP security team organizes its meetings and communication as needed.&lt;br /&gt;
&lt;br /&gt;
When the YP Security team receives a report about a potential security vulnerability, they quickly analyze and notify the reporter of the result. They might also request more information.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects the code maintained by the YP, they confidentially notify maintainers of that code and work with them to prepare a fix.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects an upstream project, the YP security team notifies the project. Usually, the upstream project analyzes the problem again. If they deem it a real security problem in their software, they develop and release a fix following their security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are generally non-public. The YP Security Team participates in the discussion as needed. They might also include the YP maintainer of the affected package.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
When the fix is publicly available, the YP security team member or the package maintainer sends patches against the YP code base, following usual procedures, including public code review.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Marta Rybczynska &#039;&#039;&#039;&amp;lt;marta DOT rybczynska [at] syslinbit [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=marta.rybczynska@syslinbit.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86002</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=86002"/>
		<updated>2023-10-18T05:28:07Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: How to report: Update in line to the SECURITY.md proposal v2&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
&lt;br /&gt;
How to Report a Potential Vulnerability?&lt;br /&gt;
========================================&lt;br /&gt;
&lt;br /&gt;
If you would like to report a public issue (for example, one with a released CVE number), please report it using the [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla].&lt;br /&gt;
&lt;br /&gt;
If you are dealing with a not-yet-released or urgent issue, please send a message to security AT yoctoproject DOT org, including as many details as possible: the layer or software module affected, the recipe and its version, and any example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them for significant issues.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source software built or used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at the Yocto Project as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and would usually report the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels including a nomination deadline. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly. The aim is to have people representing technical leadership, security knowledge and infrastructure present with enough people to provide backup/coverage but keep the notification list small enough to minimise information risk and maintain trust.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Security Team Operations ==&lt;br /&gt;
&lt;br /&gt;
The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.&lt;br /&gt;
&lt;br /&gt;
Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team. &lt;br /&gt;
&lt;br /&gt;
The YP security team organizes its meetings and communication as needed.&lt;br /&gt;
&lt;br /&gt;
When the YP Security team receives a report about a potential security vulnerability, they quickly analyze and notify the reporter of the result. They might also request more information.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects the code maintained by the YP, they confidentially notify maintainers of that code and work with them to prepare a fix.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects an upstream project, the YP security team notifies the project. Usually, the upstream project analyzes the problem again. If they deem it a real security problem in their software, they develop and release a fix following their security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are generally non-public. The YP Security Team participates in the discussion as needed. They might also include the YP maintainer of the affected package.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
When the fix is publicly available, the YP security team member or the package maintainer sends patches against the YP code base, following usual procedures, including public code review.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Marta Rybczynska &#039;&#039;&#039;&amp;lt;marta DOT rybczynska [at] syslinbit [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=marta.rybczynska@syslinbit.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85996</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85996"/>
		<updated>2023-10-17T10:00:37Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add Marta&amp;#039;s public key&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
 &lt;br /&gt;
== How to Report a Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
Please send a message to security [at] yoctoproject [dot] org, including as many details as possible: the layer or software module affected, the recipe and its version, and an example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels, including also the limit date. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Security Team Operations ==&lt;br /&gt;
&lt;br /&gt;
The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.&lt;br /&gt;
&lt;br /&gt;
Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team. &lt;br /&gt;
&lt;br /&gt;
The YP security team organizes its meetings and communication as needed.&lt;br /&gt;
&lt;br /&gt;
When the YP Security team receives a report about a potential security vulnerability, they quickly analyze and notify the reporter of the result. They might also request more information.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects the code maintained by the YP, they confidentially notify maintainers of that code and work with them to prepare a fix.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects an upstream project, the YP security team notifies the project. Usually, the upstream project analyzes the problem again. If they deem it a real security problem in their software, they develop and release a fix following their security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are generally non-public. The YP Security Team participates in the discussion as needed. They might also include the YP maintainer of the affected package.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
When the fix is publicly available, the YP security team member or the package maintainer sends patches against the YP code base, following usual procedures, including public code review.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;br /&gt;
&lt;br /&gt;
* Marta Rybczynska &#039;&#039;&#039;&amp;lt;marta DOT rybczynska [at] syslinbit [dot] com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=marta.rybczynska@syslinbit.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85995</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85995"/>
		<updated>2023-10-17T09:48:09Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Develop the part of the YP security team functioning&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
 &lt;br /&gt;
== How to Report a Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
Please send a message to security [at] yoctoproject [dot] org, including as many details as possible: the layer or software module affected, the recipe and its version, and an example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels, including also the limit date. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Security Team Operations ==&lt;br /&gt;
&lt;br /&gt;
The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.&lt;br /&gt;
&lt;br /&gt;
Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team. &lt;br /&gt;
&lt;br /&gt;
The YP security team organizes its meetings and communication as needed.&lt;br /&gt;
&lt;br /&gt;
When the YP Security team receives a report about a potential security vulnerability, they quickly analyze and notify the reporter of the result. They might also request more information.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects the code maintained by the YP, they confidentially notify maintainers of that code and work with them to prepare a fix.&lt;br /&gt;
&lt;br /&gt;
If the issue is confirmed and affects an upstream project, the YP security team notifies the project. Usually, the upstream project analyzes the problem again. If they deem it a real security problem in their software, they develop and release a fix following their security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are generally non-public. The YP Security Team participates in the discussion as needed. They might also include the YP maintainer of the affected package.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
When the fix is publicly available, the YP security team member or the package maintainer sends patches against the YP code base, following usual procedures, including public code review.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85994</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85994"/>
		<updated>2023-10-17T09:36:59Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add security team operations&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
 &lt;br /&gt;
== How to Report a Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
Please send a message to security [at] yoctoproject [dot] org, including as many details as possible: the layer or software module affected, the recipe and its version, and an example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels, including also the limit date. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Security Team Operations ==&lt;br /&gt;
&lt;br /&gt;
The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.&lt;br /&gt;
&lt;br /&gt;
Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team. &lt;br /&gt;
&lt;br /&gt;
The YP security team organizes its meetings and communication as needed.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85993</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85993"/>
		<updated>2023-10-17T09:30:39Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update LTS branches, add a link to the Releases page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
 &lt;br /&gt;
== How to Report a Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
Please send a message to security [at] yoctoproject [dot] org, including as many details as possible: the layer or software module affected, the recipe and its version, and an example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels, including also the limit date. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
* Richard Purdie &#039;&#039;&#039;&amp;lt;richard.purdie@linuxfoundation.org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]&lt;br /&gt;
&lt;br /&gt;
* Michael Halstead &#039;&#039;&#039;&amp;lt;mhalstead [at] linuxfoundation [dot] org&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
* Ross Burton &#039;&#039;&#039;&amp;lt;ross@burtonini.com&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85988</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85988"/>
		<updated>2023-10-13T15:11:59Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add lighthttpd&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* lighthttpd&lt;br /&gt;
&lt;br /&gt;
Status: not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://redmine.lighttpd.net/boards/2/topics/11188&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request merged https://github.com/nodejs/node/pull/50121 but no release yet&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85986</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85986"/>
		<updated>2023-10-13T09:44:05Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update nodejs status&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request merged https://github.com/nodejs/node/pull/50121 but no release yet&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85985</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85985"/>
		<updated>2023-10-13T09:40:25Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add tomcat&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;br /&gt;
&lt;br /&gt;
== meta-java ==&lt;br /&gt;
&lt;br /&gt;
* tomcat&lt;br /&gt;
&lt;br /&gt;
- Includes tomcat 5.5.26 which is outdated. No more analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85984</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85984"/>
		<updated>2023-10-12T17:59:11Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update status for go and nghttpd2&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Fixed (master)&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85983</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85983"/>
		<updated>2023-10-12T17:58:38Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Formatting fix&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (fixed, commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (fixed commit c24b75f027f2609dac935e8981f2eb58394b1cc6)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85982</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85982"/>
		<updated>2023-10-12T17:58:04Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update status for nghttpd2 (in master)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.57.0 (affected), commit c24b75f027f2609dac935e8981f2eb58394b1cc6&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85981</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85981"/>
		<updated>2023-10-12T17:56:55Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update the status of go (in master)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.10 (commit 262d5386c6293dbd6b9c677fbb7ed7431651db5)&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.56.0 (affected), upgrade needed to 1.57.0 by Alexandre K. Proposal on the ML https://lists.openembedded.org/g/openembedded-core/message/188968&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85980</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85980"/>
		<updated>2023-10-12T17:55:16Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update status for nghttpd2&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.7 (affected), update needed to 1.20.10 by Jose Quaresma. Proposal on the ML https://lists.openembedded.org/g/openembedded-core/message/188955&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.56.0 (affected), upgrade needed to 1.57.0 by Alexandre K. Proposal on the ML https://lists.openembedded.org/g/openembedded-core/message/188968&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85969</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85969"/>
		<updated>2023-10-11T14:35:18Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Update status of go&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.7 (affected), update needed to 1.20.10 by Jose Quaresma. Proposal on the ML https://lists.openembedded.org/g/openembedded-core/message/188955&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.56.0 (affected), upgrade needed to 1.57.0 or backport&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85968</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85968"/>
		<updated>2023-10-11T13:26:10Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add apache2&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.7 (affected), update needed to 1.20.10 by Jose Quaresma&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.56.0 (affected), upgrade needed to 1.57.0 or backport&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* apache2&lt;br /&gt;
&lt;br /&gt;
Status: Not affected&lt;br /&gt;
&lt;br /&gt;
Sources: https://chaos.social/@icing/111210915918780532&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85967</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85967"/>
		<updated>2023-10-11T13:21:32Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add ngnix&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.7 (affected), update needed to 1.20.10 by Jose Quaresma&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.56.0 (affected), upgrade needed to 1.57.0 or backport&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* ngnix&lt;br /&gt;
&lt;br /&gt;
Status: Likely not affected, configuration check needed. We MIGHT want to include the hardening patch&lt;br /&gt;
&lt;br /&gt;
Master version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/ and https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85966</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85966"/>
		<updated>2023-10-11T13:16:33Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add nodejs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.7 (affected), update needed to 1.20.10 by Jose Quaresma&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.56.0 (affected), upgrade needed to 1.57.0 or backport&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
* nodejs&lt;br /&gt;
&lt;br /&gt;
Status: Affected, via a dependency on nghttpd2&lt;br /&gt;
&lt;br /&gt;
Master version: 20.5.1, pull request pending but not release with a fix&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nodejs/node/pull/50121&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85965</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85965"/>
		<updated>2023-10-11T13:01:06Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add nghttpd2&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.7 (affected), update needed to 1.20.10 by Jose Quaresma&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
* nghttpd2&lt;br /&gt;
&lt;br /&gt;
Status: Affected&lt;br /&gt;
&lt;br /&gt;
Master version: 1.56.0 (affected), upgrade needed to 1.57.0 or backport&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
Under analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85963</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85963"/>
		<updated>2023-10-11T12:42:08Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Fix formatting&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
&lt;br /&gt;
Master version: 1.20.7 (affected), update needed to 1.20.10 by Jose Quaresma&lt;br /&gt;
&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
Under analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85962</id>
		<title>CVE-2023-44487 impact</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=CVE-2023-44487_impact&amp;diff=85962"/>
		<updated>2023-10-11T12:41:44Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Initial version&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) CVE-2023-44487 (HTTP2 RapidReset issue) =&lt;br /&gt;
&lt;br /&gt;
This is a synchronization wiki page to coordinate work on CVE-2023-44487 (known as HTTP/2 Rapid Reset issue) impact in the Yocto Project. When you have new information, do not hesitate to update/add to this page.&lt;br /&gt;
&lt;br /&gt;
== OE-core ==&lt;br /&gt;
&lt;br /&gt;
* go&lt;br /&gt;
&lt;br /&gt;
Status: Affected, confirmed&lt;br /&gt;
Master version: 1.20.7 (affected), update needed to 1.20.10 by Jose Quaresma&lt;br /&gt;
Nanbield version: Under analysis&lt;br /&gt;
Kirkstone version: Under analysis&lt;br /&gt;
Dunfell version: Under analysis&lt;br /&gt;
&lt;br /&gt;
Sources: https://go.dev/doc/devel/release#go1.20&lt;br /&gt;
&lt;br /&gt;
== meta-openembedded ==&lt;br /&gt;
&lt;br /&gt;
Under analysis&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85954</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85954"/>
		<updated>2023-10-03T15:20:07Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Fix a link to LTS. Thanks Neal!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
 &lt;br /&gt;
== How to Report a Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
Please send a message to security [at] yoctoproject [dot] org, including as many details as possible: the layer or software module affected, the recipe and its version, and an example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels, including also the limit date. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Current Yocto Project Security Team members are: &lt;br /&gt;
: : - &#039;&#039;&#039;mhalstead [at] linuxfoundation [dot] org&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
: For secure communications, please send your messages encrypted to both using the following GPG keys. &lt;br /&gt;
: Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
: Download public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&amp;amp;search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security&amp;diff=85947</id>
		<title>Security</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security&amp;diff=85947"/>
		<updated>2023-09-29T18:07:46Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Add slides from Sept 26, 2023&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Since the Yocto Project is intended to be flexible and meet the needs of many applications, we leave policy-making decisions around security to our end users. Our goal instead is to ship each release with metadata that follows best practices in that we try our best not to release recipe versions which are known to have significant security vulnerabilities. Generally this is done by upgrading recipes to newer versions that are no longer vulnerable to these issues. &lt;br /&gt;
&lt;br /&gt;
Upgrading recipes to the newer versions in the maintenance branches is not always easy, this is why we provide a patch for the existing version instead if we detect a vulnerability in a package. The patches are added to the recipes, see example below:&lt;br /&gt;
&lt;br /&gt;
  poky/recipes-connectivity/bind/bind_9.9.5.bb&lt;br /&gt;
  &lt;br /&gt;
  SRC_URI = &amp;quot;ftp://ftp.isc.org/isc/bind9/${PV}/${BPN}-${PV}.tar.gz \&lt;br /&gt;
           file://conf.patch \&lt;br /&gt;
           ...&lt;br /&gt;
           file://bind9_9_5-CVE-2014-8500.patch \&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
We provide a tool [https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/cve-check.bbclass cve-check.bbclass] to help report possible security vulnerabilities in the Yocto Project against the [http://nvd.nist.gov/home.cfm National Vulnerability Database]. Unpatched CVEs can be detected using the cve-checker which compares bitbake recipes, their versions and applied CVE patches to reported CVEs for that SW component name and version in the NVD database.&lt;br /&gt;
&lt;br /&gt;
Another good source to track reported CVEs is via the oss-security mailing list (Open Source Software Security) http://www.openwall.com/lists/oss-security/&lt;br /&gt;
&lt;br /&gt;
== Yocto Security Team ==&lt;br /&gt;
 &lt;br /&gt;
Currently the Yocto Project does not have a Security team.  We have two methods of communicating to the project. &lt;br /&gt;
&lt;br /&gt;
*  See the Yocto Project TSC Future Directions [https://wiki.yoctoproject.org/wiki/Future_Directions#Security security]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to Contact the Yocto Project regarding Security&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches. For more information including subscription information please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org (Forwards to the following addresses)&lt;br /&gt;
 &lt;br /&gt;
: : - &#039;&#039;&#039;mhalstead [at] linuxfoundation [dot] org&#039;&#039;&#039; &lt;br /&gt;
: For secure communications, please send your messages encrypted to both using the following GPG keys. &lt;br /&gt;
: Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
: Download public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead]&lt;br /&gt;
&lt;br /&gt;
Anyone can contribute with security patches as before, but those volunteering to this security team will sync/organize security related activities and take more responsibility.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream projects analyzes the problem. If they deem that it is a real security problem in their software, the project will  email the linux-distros mailing list and notify all the big Linux distributions/vendors about the existence of this vulnerability/flaw. These mailing lists are normally non-public. The project and people on the linux-distros can then agree on a release date when the flaw should be made public.&lt;br /&gt;
There is also sometimes some coordination for handling patches or backporting of patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
When the security issue is finally to be made public, normally upstream project is responsible to contact Mitre (cve.mitre.org) to get a CVE number assigned to it and copy the information to other Opens Source Security mailing lists to inform the whole world of the vulnerability.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem the Yocto&#039;s Security Team will contact linux-distros and community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
Normally big Linux vendors fix the problem if the problem affects their products.&lt;br /&gt;
Chances are that everyone from the enterprise distros to the commercial Yocto vendors will get fixes done first, but it is nice to have safety net for issues that really are specific to OE and embedded.&lt;br /&gt;
&lt;br /&gt;
== Branches maintained with security fixes  ==&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance Stable branches maintenance]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.)&lt;br /&gt;
&lt;br /&gt;
== Policy for updating package versions for the stable branches ==&lt;br /&gt;
The Yocto project purposely limits updating of packages on oe-stable releases to items that address security problems (e.g. CVEs). For packages like QEMU we avoid updating between from one &amp;quot;dot.dot&amp;quot; to another related &amp;quot;dot.dot&amp;quot; version since it has been seen in the past that even with &amp;quot;simple&amp;quot; updates, things can go wrong and a lot more testing is required to verify compatibility. Better to only add CVE patches to fix specific point problems.&lt;br /&gt;
&lt;br /&gt;
== Kernel security patches ==&lt;br /&gt;
&lt;br /&gt;
Kernel security patches are backported to Linux-yocto kernels regularly from https://www.kernel.org/&lt;br /&gt;
=== Linux-yocto ===&lt;br /&gt;
linux-yocto_3 (maintainer: Bruce Ashfield)&lt;br /&gt;
&lt;br /&gt;
=== Vendor kernels ===&lt;br /&gt;
Kernel security patches are also backported to Linux-vendor kernels from https://www.kernel.org/&lt;br /&gt;
 &lt;br /&gt;
* meta-intel (meta-intel uses Linux-yocto)&lt;br /&gt;
* meta-xilinx (meta-xilinx@lists.yoctoproject.org)&lt;br /&gt;
* meta-ti (meta-ti@yoctoproject.org)&lt;br /&gt;
* etc&lt;br /&gt;
&lt;br /&gt;
== How to test ==&lt;br /&gt;
 &lt;br /&gt;
If there is any test case for the vulnerability by the upstream project or community&lt;br /&gt;
 - Run the test to reproduce the problem and verify the correction. &lt;br /&gt;
 - Run the regression test&lt;br /&gt;
&lt;br /&gt;
If there isn’t any test case and it is complicated and time consuming to write a testcase&lt;br /&gt;
 - Run the regression test&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Regression test&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* Build the core image for at least two architectures (preferably one big-endian and one little-endian)&lt;br /&gt;
* Run ptest (for those branches/packages that there is ptest mechanism)&lt;br /&gt;
&lt;br /&gt;
== Patch name convention and commit message ==&lt;br /&gt;
&lt;br /&gt;
Security patches like any Open Source development should follow the openembedded&#039;s Guidelines:&lt;br /&gt;
*[http://openembedded.org/wiki/Commit_Patch_Message_Guidelines Commit Patch Message Guidelines]&lt;br /&gt;
*[https://www.kernel.org/doc/Documentation/SecurityBugs kernel security bugs policy] &lt;br /&gt;
&lt;br /&gt;
Note that security patches should have CVE: tag and reference to the CVE identifier both in the patch file/s and the commit message.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Ex upstream patch:&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
Please change the upstream patch &amp;quot;wscanf-allocates-too-little-memory.patch&amp;quot; to &amp;quot;CVE-2015-1472.patch&amp;quot; (or CVE-2015-1472-wscanf-allocates-too-little-memory.patch). Keep the original commit message and add reference to the CVE and upstream patch.&lt;br /&gt;
 &lt;br /&gt;
    &amp;lt;Keep the original commit message&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &lt;br /&gt;
    Upstream-Status: Accepted &amp;lt;or Backport&amp;gt;&lt;br /&gt;
    CVE: CVE-2015-8370   &lt;br /&gt;
    &lt;br /&gt;
    Reference to upstream patch:&lt;br /&gt;
    https://sourceware.org/git/?p=glibc.git;a=patch;h=5bd80bfe9ca0d955bfbbc002781bc7b01b6bcb06&lt;br /&gt;
      &lt;br /&gt;
    Signed-off-by: Joe Developer &amp;lt;joe.developer@example.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Ex meta patch:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Please make sure to add the package name in the subject and the reference to the CVE. Example for the commit message: &lt;br /&gt;
&lt;br /&gt;
    bash: CVE-2014-6278 &amp;lt;if there are multiple CVEs list all&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &amp;lt;short description&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    &amp;lt;[YOCTO #xxx] if there is any&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
    References&lt;br /&gt;
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6278&lt;br /&gt;
    https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-6278&lt;br /&gt;
    xxxx&lt;br /&gt;
    &lt;br /&gt;
    Signed-off-by: &amp;lt;your email address&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Workflow of Yocto Project&#039;s bugzilla ==&lt;br /&gt;
* To Open a Security defect go to [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security%20-%20Recipe%20Upgrade Security ‑ Recipe Upgrade]&lt;br /&gt;
** Access to this issue can only be viewed by the submitter and a small group of Bug triage folks:&lt;br /&gt;
*** Armin Kuster&lt;br /&gt;
*** Randy MacLeod&lt;br /&gt;
*** Richard Purdie&lt;br /&gt;
*** Ross Burton&lt;br /&gt;
*** Tim Orling&lt;br /&gt;
*** Stephen Jolley&lt;br /&gt;
** The normal bug triage process will be applied.&lt;br /&gt;
&lt;br /&gt;
* If the issue is already public please send the patch when available to the appropriate mailing list&lt;br /&gt;
* If the issue is private, attach a patch if available to the defect is preferred.&lt;br /&gt;
&lt;br /&gt;
== Some security related links/useful tools ==&lt;br /&gt;
&lt;br /&gt;
* [https://autobuilder.yocto.io/pub/non-release/patchmetrics/ Current CVE status for OE-Core/Poky] (generated by the Autobuilder)&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/images/5/58/Yocto_Summit_Lyon_Day1_2019.pdf#page=36 Yocto Project and CVEs, presentation by David Reyna in 2019 Yocto Developer day]&lt;br /&gt;
* [https://github.com/nluedtke/linux_kernel_cves/ Linux kernel fixed and reported CVEs in all branches and point releases]&lt;br /&gt;
** Note that cherry-picking CVE fixes for kernel is not recommended and users should merge full stable releases instead, see [http://www.kroah.com/log/blog/2018/08/24/what-stable-kernel-should-i-use/ What Stable Kernel Should I Use? by stable kernel maintainer Greg Kroah-Hartman]&lt;br /&gt;
* [http://www.cvedetails.com CVE details] &lt;br /&gt;
* [http://layers.openembedded.org/layerindex/branch/master/layer/meta-security/ Meta-security-layer]&lt;br /&gt;
* [https://docs.yoctoproject.org/dev-manual/common-tasks.html#making-images-more-secure Making Images More Secure] (Development Tasks Manual)&lt;br /&gt;
* [https://github.com/sjvermeu/cvechecker/ Cvechecker]&lt;br /&gt;
&lt;br /&gt;
== Security Issues Addressed in Yocto Releases ==&lt;br /&gt;
&lt;br /&gt;
== Current work in progress ==&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/Synchronization_CVEs Synchronization on the CVE work]&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/Security_private_reporting Security team and private reporting]&lt;br /&gt;
* [https://wiki.yoctoproject.org/wiki/File:Yocto_Project_Security_-_26_09_2023.pdf Related slides]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=File:Yocto_Project_Security_-_26_09_2023.pdf&amp;diff=85946</id>
		<title>File:Yocto Project Security - 26 09 2023.pdf</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=File:Yocto_Project_Security_-_26_09_2023.pdf&amp;diff=85946"/>
		<updated>2023-09-29T18:06:22Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Support slides for the YP weekly engineering meeting on September 26, 2023. Subjects: discussing ideas about process updates, CVE work synchronization and documentation.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Support slides for the YP weekly engineering meeting on September 26, 2023. Subjects: discussing ideas about process updates, CVE work synchronization and documentation.&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
	<entry>
		<id>https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85944</id>
		<title>Security private reporting</title>
		<link rel="alternate" type="text/html" href="https://wiki.yoctoproject.org/wiki/index.php?title=Security_private_reporting&amp;diff=85944"/>
		<updated>2023-09-28T05:48:28Z</updated>

		<summary type="html">&lt;p&gt;Marta Rybczynska: Clarify the disclosure time&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= (WIP) Security team and private reporting =&lt;br /&gt;
 &lt;br /&gt;
== How to Report a Vulnerability? ==&lt;br /&gt;
&lt;br /&gt;
Please send a message to security [at] yoctoproject [dot] org, including as many details as possible: the layer or software module affected, the recipe and its version, and an example code, if available.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039; Branches maintained with security fixes&#039;&#039;&#039;&lt;br /&gt;
----------------------------------------------&lt;br /&gt;
See [https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance Stable branches maintenance]for detailed info regarding the policies and maintenance of Stable branch.&lt;br /&gt;
&lt;br /&gt;
Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them.&lt;br /&gt;
&lt;br /&gt;
== How to Contact the Yocto Project regarding Security ==&lt;br /&gt;
&lt;br /&gt;
We have set up two security-related mailing lists:&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Public List&#039;&#039;&#039;&lt;br /&gt;
: yocto [dash] security [at] yoctoproject[dot] org&lt;br /&gt;
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].&lt;br /&gt;
&lt;br /&gt;
*  &#039;&#039;&#039;Private List&#039;&#039;&#039;&lt;br /&gt;
: security [at] yoctoproject [dot] org&lt;br /&gt;
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What you should do if you find a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source packages used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at Yocto as well.&lt;br /&gt;
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What Yocto Security Team does when it receives a security vulnerability&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
The YP Security Team team performs a quick analysis and reports the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.&lt;br /&gt;
&lt;br /&gt;
The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.&lt;br /&gt;
&lt;br /&gt;
When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;If an upstream project does not respond quickly&#039;&#039;&#039;&lt;br /&gt;
---------------------------------------------&lt;br /&gt;
If an upstream project does not fix the problem in a reasonable time, the Yocto&#039;s Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible. &lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.&lt;br /&gt;
&lt;br /&gt;
== Security Team Appointment ==&lt;br /&gt;
&lt;br /&gt;
The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels, including also the limit date. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly.&lt;br /&gt;
&lt;br /&gt;
YP Security Team members may resign at any time.&lt;br /&gt;
&lt;br /&gt;
== Current Security Team Members ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Current Yocto Project Security Team members are: &lt;br /&gt;
: : - &#039;&#039;&#039;mhalstead [at] linuxfoundation [dot] org&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
: For secure communications, please send your messages encrypted to both using the following GPG keys. &lt;br /&gt;
: Remember message headers are not encrypted so do not include sensitive information in the subject line.&lt;br /&gt;
&lt;br /&gt;
: Download public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&amp;amp;search=0x3373170601861969 Michael Halstead]&lt;/div&gt;</summary>
		<author><name>Marta Rybczynska</name></author>
	</entry>
</feed>