From: Triet Hoang <triet.hoang.dev@gmail.com>
To: sdoshi@mvista.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][scarthgap][PATCH 5/6] libxml2: Security Fix for CVE-2026-86141
Date: Fri, 25 Sep 2026 08:34:59 +0700 [thread overview]
Message-ID: <20260925013459.3957614-1-triet.hoang.dev@gmail.com> (raw)
In-Reply-To: <20260910200329.842463-5-sdoshi@mvista.com>
On Fri, 11 Sep 2026 01:33:28 +0530 Siddharth Doshi wrote:
> +---
> + xmlregexp.c | 8 ++++++--
> + 1 file changed, 6 insertions(+), 2 deletions(-)
> +
> +diff --git a/xmlregexp.c b/xmlregexp.c
> +index 5e15311..1c1b25e 100644
> +--- a/xmlregexp.c
> ++++ b/xmlregexp.c
> +@@ -702,8 +702,12 @@ xmlRegNewParserCtxt(const xmlChar *string) {
> + return(NULL);
> + memset(ret, 0, sizeof(xmlRegParserCtxt));
> + if (string != NULL)
> +- ret->string = xmlStrdup(string);
> +- ret->len = strlen((const char *) ret->string);
> ++ ret->string = xmlStrdup(string);
> ++ if (ret->string == NULL) {
> ++ xmlFree(ret);
> ++ return(NULL);
> ++ }
> ++ ret->len = strlen((const char *) ret->string);
> + ret->cur = ret->string;
> + ret->neg = 0;
> + ret->negs = 0;
> +--
The hunk keeps the brace-less if (string != NULL), so only ret->string = xmlStrdup(string);
is conditional. The NULL check below it always runs, and xmlRegNewParserCtxt() returns NULL
for every caller that passes string == NULL.
I think we need to backport [1] first before applying this patch.
[1] https://gitlab.gnome.org/GNOME/libxml2/-/commit/1a354d5b3072feaf64b5f6ea4b35e1bef35b7f65
BR,
Triet Hoang
next prev parent reply other threads:[~2026-09-25 5:35 UTC|newest]
Thread overview: 14+ 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-25 1:34 ` Triet Hoang [this message]
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 ` [scarthgap][PATCH " Siddharth Doshi
2026-09-11 14:29 ` [OE-core] " Yoann Congal
2026-09-11 19:04 ` Siddharth Doshi
2026-09-21 12:38 ` [OE-core][scarthgap][PATCH " Yoann Congal
2026-09-21 15:00 ` Yoann Congal
2026-10-02 10:59 ` 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=20260925013459.3957614-1-triet.hoang.dev@gmail.com \
--to=triet.hoang.dev@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sdoshi@mvista.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