public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [meta][PATCH 04/07] linux-yocto/6.12: update CVE exclusions (6.12.66)
Date: Mon, 26 Jan 2026 10:23:50 -0500	[thread overview]
Message-ID: <20260126152353.2328046-5-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260126152353.2328046-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: 10 changes (5 new | 5 updated): - 5 new CVEs: CVE-2026-22278, CVE-2026-23761, CVE-2026-23762, CVE-2026-23763, CVE-2026-23764 - 5 updated CVEs: CVE-2021-47746, CVE-2021-47748, CVE-2025-64097, CVE-2025-69821, CVE-2026-1328
        Date: Thu, 22 Jan 2026 16:23:30 +0000

    ]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../linux/cve-exclusion_6.12.inc               | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/meta/recipes-kernel/linux/cve-exclusion_6.12.inc b/meta/recipes-kernel/linux/cve-exclusion_6.12.inc
index 6ab3bd2bb3..52ab4eb807 100644
--- a/meta/recipes-kernel/linux/cve-exclusion_6.12.inc
+++ b/meta/recipes-kernel/linux/cve-exclusion_6.12.inc
@@ -1,11 +1,11 @@
 
 # Auto-generated CVE metadata, DO NOT EDIT BY HAND.
-# Generated at 2026-01-16 00:43:33.551663+00:00 for kernel version 6.12.65
-# From linux_kernel_cves 2026-01-16_baseline-1-gc984786b0cf
+# Generated at 2026-01-22 16:37:18.329435+00:00 for kernel version 6.12.66
+# From linux_kernel_cves cve_2026-01-22_1600Z-1-g55b49f6e4ba
 
 
 python check_kernel_cve_status_version() {
-    this_version = "6.12.65"
+    this_version = "6.12.66"
     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))
@@ -18466,7 +18466,7 @@ CVE_STATUS[CVE-2025-39820] = "fixed-version: only affects 6.15 onwards"
 
 CVE_STATUS[CVE-2025-39821] = "fixed-version: only affects 6.16 onwards"
 
-# CVE-2025-39822 needs backporting (fixed from 6.17)
+CVE_STATUS[CVE-2025-39822] = "fixed-version: only affects 6.15 onwards"
 
 CVE_STATUS[CVE-2025-39823] = "cpe-stable-backport: Backported in 6.12.45"
 
@@ -19112,7 +19112,7 @@ CVE_STATUS[CVE-2025-40145] = "fixed-version: only affects 6.15 onwards"
 
 CVE_STATUS[CVE-2025-40148] = "fixed-version: only affects 6.16 onwards"
 
-# CVE-2025-40149 needs backporting (fixed from 6.18)
+CVE_STATUS[CVE-2025-40149] = "cpe-stable-backport: Backported in 6.12.66"
 
 # CVE-2025-40150 needs backporting (fixed from 6.18)
 
@@ -19630,7 +19630,7 @@ CVE_STATUS[CVE-2025-68210] = "cpe-stable-backport: Backported in 6.12.59"
 
 CVE_STATUS[CVE-2025-68211] = "cpe-stable-backport: Backported in 6.12.59"
 
-CVE_STATUS[CVE-2025-68212] = "fixed-version: only affects 6.14 onwards"
+CVE_STATUS[CVE-2025-68212] = "fixed-version: only affects 6.15 onwards"
 
 CVE_STATUS[CVE-2025-68213] = "cpe-stable-backport: Backported in 6.12.60"
 
@@ -20074,7 +20074,7 @@ CVE_STATUS[CVE-2025-68790] = "fixed-version: only affects 6.18 onwards"
 
 CVE_STATUS[CVE-2025-68791] = "fixed-version: only affects 6.14 onwards"
 
-# CVE-2025-68792 needs backporting (fixed from 6.19rc1)
+CVE_STATUS[CVE-2025-68792] = "cpe-stable-backport: Backported in 6.12.66"
 
 CVE_STATUS[CVE-2025-68793] = "fixed-version: only affects 6.17 onwards"
 
@@ -20300,3 +20300,7 @@ CVE_STATUS[CVE-2025-71143] = "cpe-stable-backport: Backported in 6.12.64"
 
 CVE_STATUS[CVE-2025-71144] = "cpe-stable-backport: Backported in 6.12.65"
 
+CVE_STATUS[CVE-2026-22976] = "cpe-stable-backport: Backported in 6.12.66"
+
+CVE_STATUS[CVE-2026-22977] = "cpe-stable-backport: Backported in 6.12.66"
+
-- 
2.43.0



  parent reply	other threads:[~2026-01-26 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-26 15:23 [PATCH 0/7] linux-yocto: -stable and -dev updates bruce.ashfield
2026-01-26 15:23 ` [meta][PATCH 01/07] linux-yocto/6.12: update to v6.12.65 bruce.ashfield
2026-01-26 15:23 ` [meta][PATCH 02/07] linux-yocto/6.12: update CVE exclusions (6.12.65) bruce.ashfield
2026-01-26 15:23 ` [meta][PATCH 03/07] linux-yocto/6.12: update to v6.12.66 bruce.ashfield
2026-01-26 15:23 ` bruce.ashfield [this message]
2026-01-26 15:23 ` [meta][PATCH 05/07] linux-yocto/6.18: update to v6.18.6 bruce.ashfield
2026-01-26 15:23 ` [meta][PATCH 06/07] linux-yocto/6.18: update CVE exclusions (6.18.6) bruce.ashfield
2026-01-26 15:23 ` [meta][PATCH 07/07] linux-yocto-dev: update to 6.19 bruce.ashfield

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=20260126152353.2328046-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