Bug 2542559 (CVE-2026-88815) - CVE-2026-88815 perl-DBI: perl-DBI: Denial of Service via invalid memory read during numeric type casting
Summary: CVE-2026-88815 perl-DBI: perl-DBI: Denial of Service via invalid memory read ...
Keywords:
Status: NEW
Alias: CVE-2026-88815
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2542965
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-28 16:31 UTC by OSIDB Bzimport
Modified: 2026-11-12 03:07 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:76760 0 None None None 2026-10-08 06:57:41 UTC
Red Hat Product Errata RHSA-2026:76762 0 None None None 2026-10-06 20:18:00 UTC
Red Hat Product Errata RHSA-2026:77576 0 None None None 2026-10-07 13:44:11 UTC
Red Hat Product Errata RHSA-2026:85916 0 None None None 2026-10-20 11:32:05 UTC
Red Hat Product Errata RHSA-2026:99208 0 None None None 2026-11-12 03:07:51 UTC
Red Hat Product Errata RHSA-2026:99209 0 None None None 2026-11-11 22:59:12 UTC

Description OSIDB Bzimport 2026-09-28 16:31:29 UTC 
DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in sql_type_cast_svpv.

When casting to SQL_NUMERIC, sql_type_cast_svpv passes the string pointer and length of the SV to grok_number without stringifying it first. An integer (IV) or floating-point (NV) value has no valid string pointer, so grok_number reads from an invalid address, triggering a segmentation fault.

This is reachable in Perl using the sql_type_cast function:

  my $num = 42;
  DBI::sql_type_cast( $num, DBI::SQL_NUMERIC, 0 );
Comment 1 Jon Orris 2026-10-06 20:17:59 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:76762 https://access.redhat.com/errata/RHSA-2026:76762
Comment 2 Jon Orris 2026-10-07 13:44:10 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:77576 https://access.redhat.com/errata/RHSA-2026:77576
Comment 3 Jon Orris 2026-10-08 06:57:40 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:76760 https://access.redhat.com/errata/RHSA-2026:76760
Comment 4 Jon Orris 2026-10-20 11:32:04 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:85916 https://access.redhat.com/errata/RHSA-2026:85916
Comment 5 errata-xmlrpc 2026-11-11 22:59:11 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:99209 https://access.redhat.com/errata/RHSA-2026:99209
Comment 6 errata-xmlrpc 2026-11-12 03:07:50 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:99208 https://access.redhat.com/errata/RHSA-2026:99208
Note You need to log in before you can comment on or make changes to this bug.