Just fyi, the nginx vulnerabilities are all impractical to use. The bugs are use after free, which will almost definitely lead to a crash in the worker process and have them be restarted.
That itself would make it about as bad as the mp-tcp style expoits lately, but it's even weaker. If you could keep trying, you could strap an llm into figuring out a specific machine and after tons of compute eventually get out data or take controll of the nginx-owned process.
But, the restarts should restart that process, so I don't see almost any risk unless you have address randomization disabled, which would be highly unusual.
Unless I am missing something here, I see a bigger risk with an unmentioned loop that was also fixed in nginx. That one lets you make a worker thread hang, so you can disable a server until someone notices and restarts nginx. That ddos affects servers with tls1.3 support.
Also their "2root" is just a completely unrelated kernel bug they bundled for marketing, which is pissing me off tbh. All of this "security research" for marketing is the worst possible contradictory incentive. You wanna release as poorly as possible to maximize fear mongering.
They didn't even release the bug, for all we know is as convoluted to use as the mp-tcp stuff and affects basically noone. Not that the nginx side is exploitable.