Yeah. This bug has hung around but, for whatever reason, only affects some people and not others.
Here’s some threads for reference:
https://community.frame.work/t/framework-laptop-13-intel-12th-gen-stuck-on-400-mhz-or-not/72185
https://community.frame.work/t/laptop-running-at-400mhz-390mhz/23741
And here’s a post from user @mahe who came up with a workaround to the issue: