From: Valek Andrej <andrej.v@skyrain.eu>
To: raj.khem@gmail.com
Cc: openembedded-core@lists.openembedded.org,
Valek Andrej <andrej.v@skyrain.eu>
Subject: [OE-core][PATCH] glibc: Refresh CVE statuses
Date: Mon, 22 Jan 2024 09:58:05 +0100 [thread overview]
Message-ID: <20240122085805.77461-1-andrej.v@skyrain.eu> (raw)
In-Reply-To: <CAMKF1sq=5y83bJEAQEibM+UZByZ04D1bYTNzEmjOB95Oojw0oA@mail.gmail.com>
- drop irrelevant CVEs
Signed-off-by: Valek Andrej <andrej.v@skyrain.eu>
---
meta/recipes-core/glibc/glibc-version.inc | 5 -----
meta/recipes-core/glibc/glibc_2.39.bb | 2 --
2 files changed, 7 deletions(-)
diff --git a/meta/recipes-core/glibc/glibc-version.inc b/meta/recipes-core/glibc/glibc-version.inc
index 7efcd0818f6..b8f0a4a119e 100644
--- a/meta/recipes-core/glibc/glibc-version.inc
+++ b/meta/recipes-core/glibc/glibc-version.inc
@@ -7,9 +7,4 @@ GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https"
UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>\d+\.\d+(\.(?!90)\d+)*)"
-CVE_STATUS[CVE-2023-4527] = "fixed-version: Fixed in stable branch updates"
CVE_STATUS[CVE-2023-4911] = "fixed-version: Fixed in stable branch updates"
-CVE_STATUS[CVE-2023-4806] = "fixed-version: Fixed in stable branch updates"
-CVE_STATUS[CVE-2023-5156] = "fixed-version: Fixed in stable branch updates"
-CVE_STATUS[CVE-2023-4527] = "fixed-version: Fixed in stable branch updates"
-CVE_STATUS[CVE-2023-0687] = "fixed-version: Fixed in stable branch updates"
diff --git a/meta/recipes-core/glibc/glibc_2.39.bb b/meta/recipes-core/glibc/glibc_2.39.bb
index 910bbdd71b0..b5aa15ec5bb 100644
--- a/meta/recipes-core/glibc/glibc_2.39.bb
+++ b/meta/recipes-core/glibc/glibc_2.39.bb
@@ -16,8 +16,6 @@ CVE_STATUS[CVE-2019-1010025] = "disputed: \
Allows for ASLR bypass so can bypass some hardening, not an exploit in itself, may allow \
easier access for another. 'ASLR bypass itself is not a vulnerability.'"
-CVE_STATUS[CVE-2023-25139] = "cpe-stable-backport: This is integrated into the 2.37 branch as of 07b9521fc6"
-
DEPENDS += "gperf-native bison-native"
NATIVESDKFIXES ?= ""
--
2.34.1
next prev parent reply other threads:[~2024-01-22 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 19:53 [RFT][PATCH] glibc: Upgrade to 2.39 Khem Raj
2024-01-17 7:10 ` [OE-core] " Andrej Valek
2024-01-17 7:20 ` Khem Raj
2024-01-19 7:22 ` Andrej Valek
2024-01-19 14:47 ` Khem Raj
2024-01-22 8:47 ` [OE-core][PATCH] glibc: Refresh CVE statuses Valek Andrej
2024-01-22 8:58 ` Valek Andrej [this message]
2024-01-23 7:33 ` [OE-core] [RFT][PATCH] glibc: Upgrade to 2.39 Andrej Valek
2024-01-29 21:42 ` Richard Purdie
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=20240122085805.77461-1-andrej.v@skyrain.eu \
--to=andrej.v@skyrain.eu \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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