public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: yoann.congal@smile.fr
Cc: openembedded-core@lists.openembedded.org
Subject: [openembedded-core][whinlatter][PATCH 04/18] linux-yocto/6.12: update CVE exclusions (6.12.73)
Date: Thu, 23 Apr 2026 11:44:55 -0400	[thread overview]
Message-ID: <20260423154509.1933646-5-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260423154509.1933646-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: 9 changes (3 new | 6 updated): - 3 new CVEs: CVE-2026-0874, CVE-2026-0875, CVE-2026-23491 - 6 updated CVEs: CVE-2025-13601, CVE-2025-70062, CVE-2025-70063, CVE-2025-7195, CVE-2026-25500, CVE-2026-2661
        Date: Wed, 18 Feb 2026 19:58:22 +0000

    ]

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

diff --git a/meta/recipes-kernel/linux/cve-exclusion_6.12.inc b/meta/recipes-kernel/linux/cve-exclusion_6.12.inc
index 089446fe87..92a12f2c1f 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-02-16 17:20:15.768713+00:00 for kernel version 6.12.72
-# From linux_kernel_cves cve_2026-02-16_1600Z-3-gf0e5d9ffdc0
+# Generated at 2026-02-18 20:12:59.836870+00:00 for kernel version 6.12.73
+# From linux_kernel_cves cve_2026-02-18_1900Z-2-ge0bc67e5ce4
 
 
 python check_kernel_cve_status_version() {
-    this_version = "6.12.72"
+    this_version = "6.12.73"
     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))
@@ -20394,6 +20394,32 @@ CVE_STATUS[CVE-2025-71223] = "cpe-stable-backport: Backported in 6.12.70"
 
 CVE_STATUS[CVE-2025-71224] = "cpe-stable-backport: Backported in 6.12.70"
 
+CVE_STATUS[CVE-2025-71225] = "cpe-stable-backport: Backported in 6.12.70"
+
+# CVE-2025-71226 needs backporting (fixed from 6.19)
+
+# CVE-2025-71227 needs backporting (fixed from 6.19)
+
+CVE_STATUS[CVE-2025-71228] = "cpe-stable-backport: Backported in 6.12.70"
+
+# CVE-2025-71229 has no known resolution
+
+# CVE-2025-71230 has no known resolution
+
+# CVE-2025-71231 has no known resolution
+
+# CVE-2025-71232 has no known resolution
+
+# CVE-2025-71233 has no known resolution
+
+# CVE-2025-71234 has no known resolution
+
+# CVE-2025-71235 has no known resolution
+
+# CVE-2025-71236 has no known resolution
+
+# CVE-2025-71237 has no known resolution
+
 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"
@@ -20864,3 +20890,43 @@ CVE_STATUS[CVE-2026-23209] = "cpe-stable-backport: Backported in 6.12.70"
 
 # CVE-2026-23210 needs backporting (fixed from 6.19)
 
+CVE_STATUS[CVE-2026-23211] = "fixed-version: only affects 6.18 onwards"
+
+CVE_STATUS[CVE-2026-23212] = "cpe-stable-backport: Backported in 6.12.69"
+
+CVE_STATUS[CVE-2026-23213] = "cpe-stable-backport: Backported in 6.12.70"
+
+CVE_STATUS[CVE-2026-23214] = "cpe-stable-backport: Backported in 6.12.70"
+
+CVE_STATUS[CVE-2026-23215] = "cpe-stable-backport: Backported in 6.12.70"
+
+CVE_STATUS[CVE-2026-23216] = "cpe-stable-backport: Backported in 6.12.70"
+
+# CVE-2026-23217 needs backporting (fixed from 6.19)
+
+CVE_STATUS[CVE-2026-23218] = "fixed-version: only affects 6.18 onwards"
+
+CVE_STATUS[CVE-2026-23219] = "cpe-stable-backport: Backported in 6.12.70"
+
+# CVE-2026-23220 has no known resolution
+
+# CVE-2026-23221 has no known resolution
+
+# CVE-2026-23222 has no known resolution
+
+# CVE-2026-23223 has no known resolution
+
+# CVE-2026-23224 has no known resolution
+
+# CVE-2026-23225 has no known resolution
+
+# CVE-2026-23226 has no known resolution
+
+# CVE-2026-23227 has no known resolution
+
+# CVE-2026-23228 has no known resolution
+
+# CVE-2026-23229 has no known resolution
+
+# CVE-2026-23230 has no known resolution
+
-- 
2.43.0



  parent reply	other threads:[~2026-04-23 15:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 15:44 [whinlatter][PATCH 0/18] linux-yocto: stable updates to 6.12 bruce.ashfield
2026-04-23 15:44 ` [openembedded-core][whinlatter][PATCH 01/18] linux-yocto/6.12: update to v6.12.72 bruce.ashfield
2026-04-23 15:44 ` [openembedded-core][whinlatter][PATCH 02/18] linux-yocto/6.12: update CVE exclusions (6.12.72) bruce.ashfield
2026-04-23 15:44 ` [openembedded-core][whinlatter][PATCH 03/18] linux-yocto/6.12: update to v6.12.73 bruce.ashfield
2026-04-23 15:44 ` bruce.ashfield [this message]
2026-04-23 15:44 ` [openembedded-core][whinlatter][PATCH 05/18] linux-yocto/6.12: update to v6.12.74 bruce.ashfield
2026-04-23 15:44 ` [openembedded-core][whinlatter][PATCH 06/18] linux-yocto/6.12: update CVE exclusions (6.12.74) bruce.ashfield
2026-04-23 15:44 ` [openembedded-core][whinlatter][PATCH 07/18] linux-yocto/6.12: update to v6.12.76 bruce.ashfield
2026-04-23 15:44 ` [openembedded-core][whinlatter][PATCH 08/18] linux-yocto/6.12: update CVE exclusions (6.12.76) bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 09/18] linux-yocto/6.12: update to v6.12.77 bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 10/18] linux-yocto/6.12: update CVE exclusions (6.12.77) bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 11/18] linux-yocto/6.12: update to v6.12.79 bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 12/18] linux-yocto/6.12: update CVE exclusions (6.12.79) bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 13/18] linux-yocto/6.12: update to v6.12.80 bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 14/18] linux-yocto/6.12: update CVE exclusions (6.12.80) bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 15/18] linux-yocto/6.12: update to v6.12.81 bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 16/18] linux-yocto/6.12: update CVE exclusions (6.12.81) bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 17/18] linux-yocto/6.12: update to v6.12.83 bruce.ashfield
2026-04-23 15:45 ` [openembedded-core][whinlatter][PATCH 18/18] linux-yocto/6.12: update CVE exclusions (6.12.83) bruce.ashfield
2026-04-24 15:00 ` [whinlatter][PATCH 0/18] linux-yocto: stable updates to 6.12 Yoann Congal

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=20260423154509.1933646-5-bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    /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