This was reported in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=2334760

The issue is that the find-debuginfo script now fails when the do_file function exits with a non-zero code.
do_file however only has non-zero returns when it explicitly checks for a failure.
do_file doesn't have an explicit return at the end.
So the exit code of the function will be whatever the exit code of the last command in the function was.

It looks like the last thing do_file does is check if the file has multiple hard links.
Some files are hardlinked, but not to other files in the BUILDROOT, but to other dist build files.
This apparently confuses the function/script, even though it isn't fatel.

Could replicate with an hello.spec file that has something like the following in %install:

ln %

/../x

Which will the produce:

find-debuginfo: starting
Extracting debug info from 2 files
grep: /tmp/find-debuginfo.2rRIL3/linked: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.0zwSXO (%install)

upstream patch:
https://inbox.sourceware.org/debugedit/20250116180900.1158563-1-mark@klomp.org

fedora fix:
https://bodhi.fedoraproject.org/updates/FEDORA-2025-020b7e8c6a