Описание
Security update for perl-DBI
This update for perl-DBI fixes the following issues:
- CVE-2026-88815: numeric value incorrectly treated as strings in
sql_type_cast_svpvallows for process crash (bsc#1283055). - CVE-2026-88816: numeric value incorrectly treated as strings in
FetchHashKeyNameallows for process crash (bsc#1283056).
Список пакетов
SUSE Linux Enterprise Server LTSS Extended Security 12 SP5
Ссылки
- Link for SUSE-SU-2026:4442-1
- E-Mail link for SUSE-SU-2026:4442-1
- SUSE Security Ratings
- SUSE Bug 1283055
- SUSE Bug 1283056
- SUSE CVE CVE-2026-88815 page
- SUSE CVE CVE-2026-88816 page
Описание
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 );
Затронутые продукты
Ссылки
- CVE-2026-88815
- SUSE Bug 1283055
Описание
DBI versions before 1.654 for Perl incorrectly treat numeric values as strings in FetchHashKeyName. fetchrow_hashref uses the string pointer of the FetchHashKeyName attribute as the key name without stringifying it first. When FetchHashKeyName has been set to an integer (IV) or floating-point (NV) value, that pointer is invalid, so reading the key name triggers a segmentation fault. This can be triggered with the following code: my $dbh = DBI->connect( "dbi:ExampleP:", "", "", { RaiseError => 0, PrintError => 0 } ); $dbh->{FetchHashKeyName} = 42; my $sth = $dbh->prepare("select mode, size, name from ."); $sth->execute; $sth->fetchrow_hashref;
Затронутые продукты
Ссылки
- CVE-2026-88816
- SUSE Bug 1283056