Avoid use-after-free hazards in re-entrant use of pltcl.

When pltcl invokes a SQL datatype input function, it was passing a
string that is owned by the Tcl interpreter.  This is hazardous
since the input function could re-entrantly call the same Tcl
interpreter (for example, via a pltcl function in a domain check
constraint), and that call could modify or free the string we're
depending on.  Avoid the hazard by ensuring that we've pstrdup'd
whatever Tcl returned.

In all of these call sites, there's no great need to worry about
pfree'ing the extra string immediately, since we're either inside a
short-lived subtransaction or about to return from the pltcl function.
So I didn't complicate the code by doing that.

Reported-by: Anthropic OSS program
Author: Tom Lane <[email protected]>
Backpatch-through: 14
Security: CVE-2026-116323

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c0ac961cef29411fe60c5f0b576d0b7b2fdbc7c6
Author: Tom Lane <[email protected]>

Modified Files
--------------
src/pl/tcl/pltcl.c | 73 +++++++++++++++++++++++++++++++++++++++---------------
1 file changed, 53 insertions(+), 20 deletions(-)

Reply via email to