I'm trying to update OpenSSL from 3.2.4 to 3.2.5 in the Yocto project LTS branch 5.0.x (scarthgap).
The OpenSSL build and tests work, however Python3 tests fail with this change.
https://lists.openembedded.org/g/openembedded-core/message/220474

I have bisected the problem to 1432e85 .
All works when I use OpenSSL with previous commit or when I use 3.2.5 release tarball and revert this commit on top.

That is interesting that this commit was ported to all OpenSSL active branches and those don't break Python3 tests:

• Yocto 4.0.x LTS (kirkstone): openssl 3.0.17 + python 3.10.18 = SUCCESS
• Yocto 5.0.x LTS (scarthgap): openssl 3.2.5 + python 3.12.11 = FAILURE
• Yocto 5.2.x stable (walnascar): openssl 3.4.2 + python 3.13.4 = SUCCESS
• Yocto 5.3.x master/development: openssl 3.5.1 + python 3.13.5 = SUCCESS

What is also a lead is that the tests usually succeeds, but approx 25-33% cases fail.
This suggests that the new caching may return some already freed/stale data.
Can it be that the this backport into openssl-3.2 branch is broken and needs some adaptation?

/cc @levitte as author of #27551 (I didn't find PR for 3.2 branch, but this PR mentioned it)