Mariabackup currently stores the backup's binary log position in the file xtrabackup_binlog_info.
InnoDB also stores the data's corresponding binary log position in its global tablespace.
It seems as though mariabackup does not currently update the binary log position stored in InnoDB during the prepare. This has a tendency to confuse users, since they see mismatching binary log positions.
For example, they might see something like this in the prepare output written by mariabackup:
And they might see a mismatched binary log position in xtrabackup_binlog_info:
To prevent confusion, when mariabackup prepares a backup, it should probably parse the binary log position from xtrabackup_binlog_info, and then use that position to update the binary log position in InnoDB.