From: "Yoann Congal" <yoann.congal@smile.fr>
To: <hsimeliere.opensource@witekio.com>,
<openembedded-core@lists.openembedded.org>
Cc: "Bruno VERNAY" <bruno.vernay@se.com>
Subject: Re: [OE-core][scarthgap][PATCH] libcap: Fix CVE-2026-4878
Date: Mon, 06 Jul 2026 15:20:23 +0200 [thread overview]
Message-ID: <DJRIP2MOK9AQ.GHTBXXIPNQ3N@smile.fr> (raw)
In-Reply-To: <20260520091430.3075624-1-hsimeliere.opensource@witekio.com>
On Wed May 20, 2026 at 11:14 AM CEST, Hugo Simeliere via lists.openembedded.org wrote:
> From: "Hugo SIMELIERE (Schneider Electric)" <hsimeliere.opensource@witekio.com>
>
> Pick patch from [1] as mentioned in Debian report in [2].
>
> [1] https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=286ace1259992bd0c5d9016715833f2e148ac596
> [2] https://security-tracker.debian.org/tracker/CVE-2026-4878
>
> Signed-off-by: Hugo SIMELIERE (Schneider Electric) <hsimeliere.opensource@witekio.com>
> Reviewed-by: Bruno VERNAY <bruno.vernay@se.com>
> ---
> .../libcap/files/CVE-2026-4878.patch | 164 ++++++++++++++++++
> meta/recipes-support/libcap/libcap_2.69.bb | 1 +
> 2 files changed, 165 insertions(+)
> create mode 100644 meta/recipes-support/libcap/files/CVE-2026-4878.patch
Hello,
As far as I can tell, this patch is needed on wrynose.
Can you send a patch for it so I can accept this patch on scarthgap?
Thanks!
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-07-06 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 9:14 [OE-core][scarthgap][PATCH] libcap: Fix CVE-2026-4878 hsimeliere.opensource
2026-07-06 13:20 ` Yoann Congal [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-01 13:42 [OE-core] [scarthgap] [PATCH] " Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-08 14:44 ` Jeremy Rosen
2026-07-06 16:44 ` Yoann Congal
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=DJRIP2MOK9AQ.GHTBXXIPNQ3N@smile.fr \
--to=yoann.congal@smile.fr \
--cc=bruno.vernay@se.com \
--cc=hsimeliere.opensource@witekio.com \
--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