From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Collin Funk <collin.funk1@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Leonid Iziumtsev <leonid.iziumtsev@est.tech>
Subject: Re: [OE-core][PATCH 0/2] coreutils: fix multiple CVEs
Date: Sun, 02 Aug 2026 22:30:50 +0100 [thread overview]
Message-ID: <99ca1b5c9844cfb8829c1ffda00c35d239917914.camel@linuxfoundation.org> (raw)
In-Reply-To: <87a4r6jpb1.fsf@gmail.com>
On Sat, 2026-08-01 at 00:02 -0700, Collin Funk wrote:
> Richard Purdie <richard.purdie@linuxfoundation.org> writes:
>
> > Sadly, I suspect this is becoming all the more common and I share your
> > frustrations.
> >
> > We have an difficult position on whether to take things or not as we
> > probably don't have the time/experience to tell in many cases and not
> > taking a CVE fix means we'd get beaten over the head with the patch for
> > ever more as "there is a security problem" :(.
>
> Perfectly understandable.
>
> By the way, I suggest applying this patch as well [1]. In the 9.11
> release, short writes could cause issues with 'tee'. It was a silly
> mistake on my part, and cause SUSE some issues.
>
> The patch applies with NEWS removed. E.g., like this:
>
> $ sed '1,49d' 0d6fcb99d691d920961938e61c43478566ef626e.patch > fix.patch
> $ patch -p1 < fix.patch
Thanks for the pointer!
I've put that in the queue to add.
Cheers,
Richard
prev parent reply other threads:[~2026-08-02 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 11:56 [OE-core][PATCH 0/2] coreutils: fix multiple CVEs Leonid Iziumtsev
2026-07-31 11:56 ` [OE-core][PATCH 1/2] coreutils: fix CVE-2026-56391 Leonid Iziumtsev
2026-07-31 11:56 ` [OE-core][PATCH 2/2] coreutils: fix CVE-2026-56392 Leonid Iziumtsev
2026-08-01 0:11 ` [OE-core][PATCH 0/2] coreutils: fix multiple CVEs Collin Funk
2026-08-01 6:41 ` Richard Purdie
2026-08-01 7:02 ` Collin Funk
2026-08-02 21:30 ` Richard Purdie [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=99ca1b5c9844cfb8829c1ffda00c35d239917914.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=collin.funk1@gmail.com \
--cc=leonid.iziumtsev@est.tech \
--cc=openembedded-core@lists.openembedded.org \
/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