From: "Paul Barker" <paul@pbarker.dev>
To: "Prasanth Ramesh" <ragaprasanth@gmail.com>,
"paul@pbarker.dev" <paul@pbarker.dev>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"Marko, Peter" <peter.marko@siemens.com>
Subject: Re: [PATCH v2 2/2] zlib: ignore CVE-2026-76844
Date: Fri, 06 Nov 2026 09:21:23 +0000 [thread overview]
Message-ID: <DMO0N33RMCHP.JKXW47OTMMNB@pbarker.dev> (raw)
In-Reply-To: <CAG7eodHPk6FYtFE7-M35ymXqH40RpYEHkdoUbkcgpNKaSdYC0g@mail.gmail.com>
On Fri Nov 6, 2026 at 8:28 AM GMT, Prasanth Ramesh wrote:
> Hi Paul,
>
> are you ok with dropping 2/2?
Hi Prasanth,
https://app.opencve.io/cve/CVE-2026-76844 still shows this as a zlib
CVE, but unaffected after v1.3.2. So yes, this can probably be dropped.
Hopefully the upstream data will get fixed soon.
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-11-06 9:21 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 ` [PATCH v2 2/2] zlib: ignore CVE-2026-76844 Prasanth R
2026-11-06 6:53 ` Marko, Peter
2026-11-06 8:13 ` Prasanth Ramesh
2026-11-06 8:28 ` Prasanth Ramesh
2026-11-06 9:21 ` Paul Barker [this message]
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=DMO0N33RMCHP.JKXW47OTMMNB@pbarker.dev \
--to=paul@pbarker.dev \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=ragaprasanth@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 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.