Another exposure, left-field
(Anyone else remember how Ken Thompson backdoored every unix? Twiddled a core compiler.)
There's another major risk arisen recently, not obviously nation-state but ideological, and a lot larger/wider than most nation-states can manage.
You may have noticed the Rust OSS community has been hijacked by people you could generously describe as psychotic: anti-pleb, anti-West, anti-personalchoice, anti- pretty much everything that's created the society & societal wealth that lets them play on computers with their adopted Language Of Virtue.
You may also have noticed that they've done a systemd: forced out previous code versions in favour of their own language's copies of same, across multiple distros.
This is parTICularly insane, given that their versions are regressions: failing even basic Unit Tests(!).
It is also parTICularly odd, that they've focussed in the first instance on very simple&reliable but core utilities which every box and —more importantly— every complex or large installation critically relies on.
Eg NTP. Heard of any egregious memory safety bugs in NTP in the last many years? Nor have I. But tell you what, if every box in a high-availability replicating database backend switched to different times all of a sudden, WOULDN'T we have fun watching the front-end's service-provision collapse in a shower of "argh".
An oddly fawning Ubuntu team post credited the entire drive to swap out long-standing battle-tested functional code for test-failing regressions of Rust code, to one particular group. That group and its funders likewise seem obsessed with swerving the usual memory-bug risky culprits in favour of taking over core low level tools which lend themselves very well to sabotage. sudo, for example.
Check out Trifecta Tech Foundation then their funders. Eg, one of their funders proudly boasts that their code has now completely replaced the NTP servers for Lets Encrypt.
Worth noting that Rust's compiler is now Rust. Anyone else remember how Ken Thompson backdoored every unix?
HE did it innocuously, just as a mental exercise and also to point up the security exposure.
Diametrically-opposite-wise, given the anti-pleb psychosis (proudly) displayed by many of the Rust community, we are now looking at all but a handful of Linux distros now carrying material risk of that exposure being not just created but "weaponised".
I would not be deploying a Rust-affected Linux for anything critical until I'd seen the results of some pentesting teams reverse-engineering the binaries.