Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL

Jim Jones <jim.jones@uni-muenster.de>

From: Jim Jones <jim.jones@uni-muenster.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, pgsql-bugs@lists.postgresql.org, maralist86@mail.ru
Date: 2025-06-08T17:00:25Z
Lists: pgsql-bugs
On 08.06.25 17:40, Tom Lane wrote:
> Our risk-aversion level rises steadily over the course of a release
> cycle, and is pretty high post beta1.  While I think the problems
> we're trying to fix here are real, they are very low-probability
> (I don't recall hearing any field reports traceable to this).
> And you have to remember there is also some risk of introducing
> new bugs.  On balance it's not a change I would back-patch, and
> at this point v18 is pretty close to being a stable branch so
> it's not getting fixes we wouldn't back-patch, unless that's
> because they are in new-in-18 code.

Makes sense. Thanks for the clarification!

Best regards, Jim



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. xml2: Fix failure with xslt_process() under -fsanitize=undefined

  2. Fix misuse of "volatile" in xml.c

  3. xml2: Improve error handling of libxml2 calls

  4. Improve error handling of libxml2 calls in xml.c