Live › vulnerability › CVE-2026-111879
Go to dashboardDBI before 1.656 for Perl leaks an exclusive file lock when opening a DBD::DBM table fails on a bad dbm_mldbm or dbm_type value or a missing data file. A later open of the same table then blocks indefinitely, which is a denial of service rather than code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that use Perl DBI with the DBD::DBM driver and let a caller influence the dbm_mldbm or dbm_type values through the DSN or connect attributes. Systems that only use other database drivers, or hard-code DBM settings, are not exposed to the hang.
No product ranges from the sources yet.
perl -MDBI -e 'print $DBI::VERSION'grep -r 'DBD::DBM' .1.656 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
DBI versions before 1.656 for Perl hang on a later open of a DBD::DBM table because a failed open_data does not release the table's lock.
open_data creates the table's lock file and takes an exclusive flock on it for a CREATE, before the checks that can croak: a dbm_mldbm value that is not a module name, a failing tie, or a missing data file. The croak unwinds before the table object is blessed, so nothing releases the lock, and the meta data holding the open descriptor stays cached on the database handle.
The dbm_mldbm and dbm_type values come from the DSN or the connect attributes, so a caller that chooses the serializer or the storage backend can trigger the failure.
The flock has no timeout, so a later open of that table (even through a separate database handle) blocks for as long as the handle holding the stale lock lives, in the same process or any other.
This page as .md · .json · in your agent: get_signal("CVE-2026-111879")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.