Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, 13952878799(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
Date: 2025-10-23 00:29:19
Message-ID: aPl235F3k3ZDeAfj@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Oct 21, 2025 at 11:06:19AM -0400, Tom Lane wrote:
> We'd really need to see a concrete example to decide whether this is
> a PG bug or user error. I think the SASL stuff is sufficiently poorly
> tested that it could be a previously-unknown PG bug, but it's not clear.

[ .. double-checking the code .. ]

FWIW, I doubt that this is something we need to worry about and I
suspect that there is no action item here. dblink and WAL receivers
do their stuff so as the main backend code does not link with libpq,
and I doubt that we'd ever want to enter in the territory where
FRONTEND becomes a thing in libpq.

Of course, I may prove wrong.

> So: test case, please.

Yes.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ishan Arunkumar Joshi 2025-10-23 04:48:20 RE: BUG #18942 and BUG #18938 solution available in Pg16 latest release 16.10
Previous Message David Rowley 2025-10-23 00:20:52 Re: ERROR: XX000: could not find memoization table entry (reproducible)