All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Barker" <paul@pbarker.dev>
To: "Marko, Peter" <Peter.Marko@siemens.com>,
	"Paul Barker" <paul@pbarker.dev>,
	"Prasanth R" <ragaprasanth@gmail.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "Prasanth R" <prasanth.r@lineo.co.jp>
Subject: Re: [OE-core] [PATCH] zlib: patch CVE-2026-85091 and CVE-2026-76844
Date: Thu, 05 Nov 2026 15:17:08 +0000	[thread overview]
Message-ID: <DMNDKX7R5FND.2I2DXKC6MRMXO@pbarker.dev> (raw)
In-Reply-To: <AS8PR10MB50736C390B00B646F697DCB2FD772@AS8PR10MB5073.EURPRD10.PROD.OUTLOOK.COM>

>> -----Original Message-----
>> From: openembedded-core@lists.openembedded.org <openembedded-
>> core@lists.openembedded.org> On Behalf Of Paul Barker
>> Sent: Thursday, November 5, 2026 4:03 PM
>> To: Prasanth R <ragaprasanth@gmail.com>; openembedded-
>> core@lists.openembedded.org
>> Cc: Prasanth R <prasanth.r@lineo.co.jp>
>> Subject: Re: [OE-core] [PATCH] zlib: patch CVE-2026-85091 and CVE-2026-
>> 76844
>> 
>> 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

On Thu Nov 5, 2026 at 3:08 PM GMT, Peter Marko wrote:
> Also note that for master, there is a new tag since yesterday.
> Patches are then only for the older releases.

Thanks for the update Peter.

In this case we just need the CVE_STATUS assignment for CVE-2026-76844,
as CVE-2026-85091 is fixed in zlib 1.4.

Best regards,

-- 
Paul Barker


      reply	other threads:[~2026-11-05 15:17 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
2026-11-05 15:08   ` [OE-core] " Marko, Peter
2026-11-05 15:17     ` Paul Barker [this message]

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=DMNDKX7R5FND.2I2DXKC6MRMXO@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=Peter.Marko@siemens.com \
    --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 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.