> Exploiting this bug to mount an Remote Code Execution attack (RCE) can't be ruled out.
In all seriousness, “remote” in this case means attacker controlled.
If not, and all exploits are attacker controlled, it sounds like all exploits are RCE.
EDIT I guess I have to weaken the last condition since we haven't proved all exploits are "code execution", but we have at least proved all exploits are "remote".
"Yeah this is a classic double free. We can't think of a way to transform it into a RCE or something like that, we've also failed at having LLMs do it so far. but in the current climate it could happen so we humbly ask the tag of most dangerous vulnerability please. Not just this disclaimer. We want 9.9 CVE that says RCE!!"
This is ridiculous.
It's still a critical bug, just would not call it a prime example of rce.
I thought we reached the point a few years ago where the assumed probability this can be done is 100% ?
If you believe an LLM can generate an exploit for this - feel free to post one.
Quit writing memory free errors in software. Prove your software is safe, not prove that it's not exploitable.
At first I thought the whole Linux everything is a CVE was kind of annoying, but over time, especially with automated exploit finding it really has shown to be in front of what was about to happen.