From: "Paul Barker" <paul@pbarker.dev>
To: "Prasanth R" <ragaprasanth@gmail.com>,
<openembedded-core@lists.openembedded.org>
Cc: "Prasanth R" <prasanth.r@lineo.co.jp>
Subject: Re: [PATCH] zlib: patch CVE-2026-85091 and CVE-2026-76844
Date: Thu, 05 Nov 2026 15:03:04 +0000 [thread overview]
Message-ID: <DMNDA5FMY9UQ.1GQQ7M7RMMVH4@pbarker.dev> (raw)
In-Reply-To: <20261030050531.720920-1-prasanth.r@lineo.co.jp>
On Fri Oct 30, 2026 at 5:05 AM GMT, Prasanth R wrote:
> From: Prasanth R <ragaprasanth@gmail.com>
>
> Backport the upstream fix. It covers both CVEs.
> CVE-2026-85091 & CVE-2026-76844
Hi Prasanth,
This troubled me as two CVE ids shouldn't really be pointing at a single
simple fix. So I looked into it some more...
CVE-2026-76844 currently points at zlib in error [1], so this one should
be resolved by setting CVE_STATUS rather than by assigning two CVE ids
to the same patch. Please could you send a v2 for CVE-2026-85091, along
with a CVE_STATUS assignment for CVE-2026-76844?
[1]: https://github.com/madler/zlib/issues/1330
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-11-05 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 5:05 [PATCH] zlib: patch CVE-2026-85091 and CVE-2026-76844 Prasanth R
2026-11-05 15:03 ` Paul Barker [this message]
2026-11-05 15:08 ` [OE-core] " Marko, Peter
2026-11-05 15:17 ` Paul Barker
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=DMNDA5FMY9UQ.1GQQ7M7RMMVH4@pbarker.dev \
--to=paul@pbarker.dev \
--cc=openembedded-core@lists.openembedded.org \
--cc=prasanth.r@lineo.co.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox