The L3 finding on Linux is likely caused by the C3 entry cache flush, which goes away in our upcoming 6.1 kernel. It doesn't affect most game workloads but can be a real performance problem in some specific cases.
https://lore.kernel.org/lkml/CAJZ5v0jWX=H=aZ25PzHdH05bRJvtYb...
The way the benchmark works likely triggers it consistently.