From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [meta][PATCH 04/11] linux-yocto/6.18: update CVE exclusions (6.18.16)
Date: Mon, 23 Mar 2026 09:50:50 -0400 [thread overview]
Message-ID: <20260323135057.1605923-5-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260323135057.1605923-1-bruce.ashfield@gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Data pulled from: https://github.com/CVEProject/cvelistV5
1/1 [
Author: cvelistV5 Github Action
Email: github_action@example.com
Subject: 12 changes (4 new | 8 updated): - 4 new CVEs: CVE-2024-14027, CVE-2025-70040, CVE-2025-70060, CVE-2026-3588 - 8 updated CVEs: CVE-2025-69219, CVE-2026-22457, CVE-2026-22460, CVE-2026-27332, CVE-2026-27379, CVE-2026-27382, CVE-2026-27384, CVE-2026-27386
Date: Mon, 9 Mar 2026 16:04:20 +0000
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
.../linux/cve-exclusion_6.18.inc | 30 ++++++++++++++-----
1 file changed, 23 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-kernel/linux/cve-exclusion_6.18.inc b/meta/recipes-kernel/linux/cve-exclusion_6.18.inc
index 4afd58e924..e8173c4c9f 100644
--- a/meta/recipes-kernel/linux/cve-exclusion_6.18.inc
+++ b/meta/recipes-kernel/linux/cve-exclusion_6.18.inc
@@ -1,11 +1,11 @@
# Auto-generated CVE metadata, DO NOT EDIT BY HAND.
-# Generated at 2026-02-23 04:32:17.926406+00:00 for kernel version 6.18.13
-# From linux_kernel_cves cve_2026-02-23_0300Z-2-gda53cb14ddd
+# Generated at 2026-03-09 16:24:50.284184+00:00 for kernel version 6.18.16
+# From linux_kernel_cves cve_2026-03-09_1500Z-2-g02517aa779f
python check_kernel_cve_status_version() {
- this_version = "6.18.13"
+ this_version = "6.18.16"
kernel_version = d.getVar("LINUX_VERSION")
if kernel_version != this_version:
bb.warn("Kernel CVE status needs updating: generated for %s but kernel is %s" % (this_version, kernel_version))
@@ -9032,6 +9032,8 @@ CVE_STATUS[CVE-2023-54326] = "fixed-version: Fixed from version 6.5"
CVE_STATUS[CVE-2023-7324] = "fixed-version: Fixed from version 6.3"
+CVE_STATUS[CVE-2024-14027] = "fixed-version: Fixed from version 6.13"
+
CVE_STATUS[CVE-2024-26581] = "fixed-version: Fixed from version 6.8"
CVE_STATUS[CVE-2024-26582] = "fixed-version: Fixed from version 6.8"
@@ -20396,12 +20398,8 @@ CVE_STATUS[CVE-2025-71224] = "cpe-stable-backport: Backported in 6.18.10"
CVE_STATUS[CVE-2025-71225] = "cpe-stable-backport: Backported in 6.18.10"
-CVE_STATUS[CVE-2025-71226] = "cpe-stable-backport: Backported in 6.18.10"
-
CVE_STATUS[CVE-2025-71227] = "cpe-stable-backport: Backported in 6.18.10"
-CVE_STATUS[CVE-2025-71228] = "cpe-stable-backport: Backported in 6.18.10"
-
CVE_STATUS[CVE-2025-71229] = "cpe-stable-backport: Backported in 6.18.11"
CVE_STATUS[CVE-2025-71230] = "cpe-stable-backport: Backported in 6.18.11"
@@ -20420,6 +20418,8 @@ CVE_STATUS[CVE-2025-71236] = "cpe-stable-backport: Backported in 6.18.11"
CVE_STATUS[CVE-2025-71237] = "cpe-stable-backport: Backported in 6.18.11"
+CVE_STATUS[CVE-2025-71238] = "cpe-stable-backport: Backported in 6.18.13"
+
CVE_STATUS[CVE-2026-22976] = "cpe-stable-backport: Backported in 6.18.6"
CVE_STATUS[CVE-2026-22977] = "cpe-stable-backport: Backported in 6.18.6"
@@ -20930,3 +20930,19 @@ CVE_STATUS[CVE-2026-23229] = "cpe-stable-backport: Backported in 6.18.11"
CVE_STATUS[CVE-2026-23230] = "cpe-stable-backport: Backported in 6.18.11"
+CVE_STATUS[CVE-2026-23231] = "cpe-stable-backport: Backported in 6.18.14"
+
+CVE_STATUS[CVE-2026-23232] = "fixed-version: only affects 6.19 onwards"
+
+CVE_STATUS[CVE-2026-23233] = "cpe-stable-backport: Backported in 6.18.13"
+
+CVE_STATUS[CVE-2026-23234] = "cpe-stable-backport: Backported in 6.18.13"
+
+CVE_STATUS[CVE-2026-23235] = "cpe-stable-backport: Backported in 6.18.13"
+
+CVE_STATUS[CVE-2026-23236] = "cpe-stable-backport: Backported in 6.18.13"
+
+CVE_STATUS[CVE-2026-23237] = "cpe-stable-backport: Backported in 6.18.13"
+
+CVE_STATUS[CVE-2026-23238] = "cpe-stable-backport: Backported in 6.18.13"
+
--
2.43.0
next prev parent reply other threads:[~2026-03-23 13:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:50 [PATCH 0/11] linux-yocto: consolidated pull request bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 01/11] linux-yocto/6.18: genericarm64: enable additional qcom drivers bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 02/11] linux-yocto/6.18: genericarm64: fix configuration audit warning bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 03/11] linux-yocto/6.18: update to v6.18.16 bruce.ashfield
2026-03-23 13:50 ` bruce.ashfield [this message]
2026-03-23 13:50 ` [meta][PATCH 05/11] linux-yocto/6.18: update to v6.18.18 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 06/11] linux-yocto/6.18: update CVE exclusions (6.18.18) bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 07/11] linux-yocto-dev: bump to v7.0 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 08/11] linux-yocto/6.18: update to v6.18.19 bruce.ashfield
2026-03-23 22:15 ` Richard Purdie
2026-03-24 0:25 ` Bruce Ashfield
2026-03-23 13:50 ` [meta][PATCH 09/11] linux-yocto/6.18: update CVE exclusions (6.18.19) bruce.ashfield
2026-03-23 13:50 ` [meta-yocto-bsp][PATCH 10/11] yocto-bsps: update to v6.18.18 bruce.ashfield
2026-03-23 14:01 ` Patchtest results for " patchtest
2026-03-23 13:50 ` [meta-yocto-bsp][PATCH 11/11] yocto-bsps: update to v6.18.19 bruce.ashfield
2026-03-23 14:01 ` Patchtest results for " patchtest
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260323135057.1605923-5-bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox