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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-22 17:21
- References+1 references (now 4)NVD modified 2026-10-21 01:17
- StatusPublished → ReceivedNVD modified 2026-10-21 01:17
- StatusReceived → PublishedNVD modified 2026-10-20 21:24
- First seenunscoredNVD modified 2026-10-20 22:18
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.