All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prasanth R <ragaprasanth@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: paul@pbarker.dev, peter.marko@siemens.com,
	Prasanth R <ragaprasanth@gmail.com>
Subject: [PATCH v2 2/2] zlib: ignore CVE-2026-76844
Date: Fri,  6 Nov 2026 10:13:24 +0900	[thread overview]
Message-ID: <20261106011324.626292-2-ragaprasanth@gmail.com> (raw)
In-Reply-To: <20261106011324.626292-1-ragaprasanth@gmail.com>

CVE-2026-76844 is a webpack-dev-middleware CVE. Its record got the zlib
gz_vacate details by mistake; the zlib CVE for that bug is
CVE-2026-85091 [1].

[1] https://github.com/madler/zlib/issues/1330

AI-Generated: Uses Claude
Signed-off-by: Prasanth R <prasanth.r@lineo.co.jp>
---
 meta/recipes-core/zlib/zlib_1.4.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-core/zlib/zlib_1.4.bb b/meta/recipes-core/zlib/zlib_1.4.bb
index 18b27df878..2bc1967c0e 100644
--- a/meta/recipes-core/zlib/zlib_1.4.bb
+++ b/meta/recipes-core/zlib/zlib_1.4.bb
@@ -47,3 +47,5 @@ BBCLASSEXTEND = "native nativesdk"
 
 # Adding 'CVE_PRODUCT' to avoid false detection of CVEs
 CVE_PRODUCT = "zlib:zlib gnu:zlib"
+
+CVE_STATUS[CVE-2026-76844] = "cpe-incorrect: this CVE is for webpack-dev-middleware, the zlib details were added in error"
-- 
2.34.1


  reply	other threads:[~2026-11-06  1:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  1:13 [PATCH v2 1/2] zlib: upgrade 1.3.2 -> 1.4 Prasanth R
2026-11-06  1:13 ` Prasanth R [this message]
2026-11-06  6:53   ` [PATCH v2 2/2] zlib: ignore CVE-2026-76844 Marko, Peter
2026-11-06  8:13     ` Prasanth Ramesh
2026-11-06  8:28       ` Prasanth Ramesh
2026-11-06  9:21         ` Paul Barker
2026-11-06  9:22           ` Prasanth Ramesh

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=20261106011324.626292-2-ragaprasanth@gmail.com \
    --to=ragaprasanth@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    --cc=peter.marko@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.