FYI, a contributor has submitted a patch to the kernel Bugzilla [1] and it indeed fixed the issue for the packages where I was seeing this. Let's hope it gets recognized and accepted soon. Best, Christian [1]: https://bugzilla.kernel.org/show_bug.cgi?id=218916