From: "Siddharth Doshi" <sdoshi@mvista.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [scarthgap][PATCH 1/6] libxml2: Security Fix for CVE-2026-86137
Date: Fri, 11 Sep 2026 06:24:01 -0700 [thread overview]
Message-ID: <308852.1789133041123096150@lists.openembedded.org> (raw)
In-Reply-To: <DLCIC1493YTD.2KR894JSU7SKE@smile.fr>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
Hello Yoann,
Richard sent a patch to master for libxml2--> libxml2: upgrade 2.15.3 -> 2.15.4 which fixes these CVE's
(ref: https://lists.openembedded.org/g/openembedded-core/message/245203 )
The same patch sent by Richard is applicable to wrynose too and considering that i didn't send a patch to version upgrade libxml2 for wrynose.
However, if you still feel i should send the same thing for wrynose, i would do it.
Could you let me know i should proceed for it according to you ?
Regards,
Siddharth
[-- Attachment #2: Type: text/html, Size: 689 bytes --]
next prev parent reply other threads:[~2026-09-11 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 20:03 [OE-core][scarthgap][PATCH 1/6] libxml2: Security Fix for CVE-2026-86137 Siddharth
2026-09-10 20:03 ` [OE-core][scarthgap][PATCH 2/6] libxml2: Security Fix for CVE-2026-86138 Siddharth
2026-09-10 20:03 ` [OE-core][scarthgap][PATCH 3/6] libxml2: set CVE_STATUS for CVE-2026-86139 Siddharth
2026-09-10 20:03 ` [OE-core][scarthgap][PATCH 4/6] libxml2: Security Fix for CVE-2026-86140 Siddharth
2026-09-10 20:03 ` [OE-core][scarthgap][PATCH 5/6] libxml2: Security Fix for CVE-2026-86141 Siddharth
2026-09-10 20:03 ` [OE-core][scarthgap][PATCH 6/6] libxml2: Security Fix for CVE-2026-86143 Siddharth
2026-09-11 13:05 ` [OE-core][scarthgap][PATCH 1/6] libxml2: Security Fix for CVE-2026-86137 Yoann Congal
2026-09-11 13:24 ` Siddharth Doshi [this message]
2026-09-11 14:29 ` [OE-core] [scarthgap][PATCH " Yoann Congal
2026-09-11 19:04 ` Siddharth Doshi
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=308852.1789133041123096150@lists.openembedded.org \
--to=sdoshi@mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.