The vulnerability stems from improper handling of volume connection information during live migration rollback. The refresh_conn_infos function was modified in the patch to explicitly check for refresh_connection_info method existence before calling it. The pre-patch version blindly attempted to call this method on all devices via map, which: 1) Didn't work in Python 3 (map returns iterator), 2) Risked skipping updates if any device lacked the method. This could leave outdated connection_info (e.g., LUN IDs) in the database after failed migrations, enabling access to wrong volumes. The added test in test_block_device.py confirms only DriverVolumeBlockDevice-derived devices should refresh their connection_info.