From: "Yoann Congal" <yoann.congal@smile.fr>
To: <hthakar@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap][PATCH 1/1] openssh: fix CVE-2026-106587
Date: Sat, 21 Nov 2026 00:05:43 +0100 [thread overview]
Message-ID: <DN0EXVAABCIP.YDZIYTDBHKP0@smile.fr> (raw)
In-Reply-To: <20261016035448.3083867-2-hthakar@cisco.com>
On Fri Oct 16, 2026 at 5:54 AM CEST, Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> From: Hetvi Thakar <hthakar@cisco.com>
>
> This patch applies the upstream fix as referenced in [2],
> using the commit shown in [1]..
>
> [1] https://github.com/openssh/openssh-portable/commit/526fd2771342f36142099bec82c49ce0457c5016
> [2] https://nvd.nist.gov/vuln/detail/CVE-2026-106587
>
> Signed-off-by: Hetvi Thakar <hthakar@cisco.com>
> ---
> .../openssh/openssh/CVE-2026-106587.patch | 76 +++++++++++++++++++
> .../openssh/openssh_9.6p1.bb | 1 +
> 2 files changed, 77 insertions(+)
> create mode 100644 meta/recipes-connectivity/openssh/openssh/CVE-2026-106587.patch
Hello,
This patch is blocked pending a blacksail backport:
See equivalent wrynose thread from Mon, 09 Nov 2026:
https://lore.kernel.org/all/DMQR3DP72ES8.3KANJDXOTSO63@smile.fr/
I will now drop this patch. Please send a new submission if the above
situation changes.
Regards,
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-11-20 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 3:54 [OE-core][scarthgap][PATCH 0/1] openssh: Security Fix Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-16 3:54 ` [OE-core][scarthgap][PATCH 1/1] openssh: fix CVE-2026-106587 Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-20 23:05 ` Yoann Congal [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=DN0EXVAABCIP.YDZIYTDBHKP0@smile.fr \
--to=yoann.congal@smile.fr \
--cc=hthakar@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