pgsql: Be more wary about constant's datatype in scalarineqsel(). - Mailing list pgsql-committers

From Noah Misch
Subject pgsql: Be more wary about constant's datatype in scalarineqsel().
Date
Msg-id E1wtQFt-00000000yGC-0Sw2@gemulon.postgresql.org
Whole thread
List pgsql-committers
Be more wary about constant's datatype in scalarineqsel().

The special case here for estimating conditions involving a ctid
column failed to check that the RHS constant is of type tid.
While that'd always be true for the built-in operators that
reference this selectivity estimator, a maliciously constructed
operator could provide a user-controlled Datum value that would
get interpreted as an ItemPointer pointer.  That at least risks
SIGSEGV, and perhaps with a bit of sweat it could be used for
server memory disclosure.

Reported-by: Hcamael <baiyjrh@gmail.com>
Author: Tom Lane <tgl@sss.pgh.pa.us>
Reviewed-by: Noah Misch <noah@leadboat.com>
Backpatch-through: 14
Security: CVE-2026-14668

Branch
------
REL_16_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/591192e2ec76922f847e39e01d4d4d3ababc5178
Author: Tom Lane <tgl@sss.pgh.pa.us>

Modified Files
--------------
src/backend/utils/adt/selfuncs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)


Attachment

pgsql-committers by date:

Previous
From: Noah Misch
Date:
Subject: pgsql: Check for USAGE privilege on the composite type in ALTER TABLE O
Next
From: Noah Misch
Date:
Subject: pgsql: Harden PL/Perl code against "tied" Perl arrays and hashes.