PT-2026-119527 · Undefined · Undefined

CVE-2026-111879

·

Published

2026-10-20

·

Updated

2026-10-20

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.

Improper Locking

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-111879

Affected Products

Undefined