From: "Yoann Congal" <yoann.congal@smile.fr>
To: <peter.marko@siemens.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [scarthgap][PATCH 1/3] cpio: patch CVE-2026-66485
Date: Fri, 28 Aug 2026 10:25:18 +0200 [thread overview]
Message-ID: <DL0FM099GEIW.TMGQI3PXEOAU@smile.fr> (raw)
In-Reply-To: <20260815190824.2980891-1-peter.marko@siemens.com>
On Sat Aug 15, 2026 at 9:08 PM CEST, Peter Marko via lists.openembedded.org wrote:
> From: Peter Marko <peter.marko@siemens.com>
>
> Pick patch mentioned in NVD CVE description.
>
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> (From OE-Core rev: c105fbf82e2f50b05dc680e0601bf0ea3198e58c)
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> ---
> meta/recipes-extended/cpio/cpio_2.15.bb | 1 +
> .../cpio/files/CVE-2026-66485.patch | 210 ++++++++++++++++++
> 2 files changed, 211 insertions(+)
> create mode 100644 meta/recipes-extended/cpio/files/CVE-2026-66485.patch
Hello,
It looks like this series triggers ptests issues:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/61/builds/4362
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/73/builds/4378
https://valkyrie.yocto.io/pub/non-release/20260824-88/testresults/qemux86-64-ptest/core-image-ptest-cpio/log.do_testimage.311338.20260824214940
| FAIL: CVE-2019-14866 (tar header size overflow)
Can you look into this?
Thanks!
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-08-28 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 19:08 [scarthgap][PATCH 1/3] cpio: patch CVE-2026-66485 Peter Marko
2026-08-15 19:08 ` [scarthgap][PATCH 2/3] cpio: patch CVE-2026-66484 Peter Marko
2026-08-15 19:08 ` [scarthgap][PATCH 3/3] cpio: patch CVE-2026-66486 Peter Marko
2026-08-28 8:25 ` Yoann Congal [this message]
2026-08-28 8:29 ` [OE-core] [scarthgap][PATCH 1/3] cpio: patch CVE-2026-66485 Yoann Congal
2026-09-12 19:15 ` Marko, Peter
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=DL0FM099GEIW.TMGQI3PXEOAU@smile.fr \
--to=yoann.congal@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox