From: "Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)" <sudumbha@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442
Date: Wed, 13 May 2026 10:39:44 -0700 [thread overview]
Message-ID: <2126378.1778693984779046075@lists.openembedded.org> (raw)
In-Reply-To: <DICS8ZZ99Q7C.25QI9TUSM1VCB@smile.fr>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
Hi Yoann,
Thank you for your review.
I have regenerated the patch and address the issue which you have highlighted. I have resent the v2 here:
[scarthgap][PATCH v2 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442 ( https://lists.openembedded.org/g/openembedded-core/message/236997 )
[scarthgap][PATCH v2 2/2] binutils: fix CVE-2026-4647 ( https://lists.openembedded.org/g/openembedded-core/message/236998 )
Thanks and Regards,
Sudhir
[-- Attachment #2: Type: text/html, Size: 742 bytes --]
prev parent reply other threads:[~2026-05-13 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 14:23 [OE-core][scarthgap][PATCH 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-05-02 14:23 ` [OE-core][scarthgap][PATCH 2/2] binutils: fix CVE-2026-4647 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-05-07 22:03 ` [OE-core][scarthgap][PATCH 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442 Yoann Congal
2026-05-13 17:27 ` [OE-core][scarthgap][PATCH v2 " Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-05-13 17:27 ` [OE-core][scarthgap][PATCH v2 2/2] binutils: fix CVE-2026-4647 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-03 21:09 ` Yoann Congal
2026-07-06 10:43 ` Yoann Congal
2026-06-03 21:02 ` [OE-core][scarthgap][PATCH v2 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442 Yoann Congal
2026-05-13 17:39 ` Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco) [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=2126378.1778693984779046075@lists.openembedded.org \
--to=sudumbha@cisco.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