That and the kernel can be patched, which is the much bigger concern (and what I found a bit confusing about the quote conversation from before, patching is always a concern). Attack vectors are always present, its when the kernel itself is ironed out that is more troublesome. In fact that's usually why many kernel exploits remain unreleased ad infinitum, because if you lose the kernel vuln, you may never recover it or an equivalent one and it stifles further tinkering.
Which, again, is why I am dubious on this being capable on current FW since I'd have expected some degree of caution from the devs on it, unless they genuinely don't care if its patched and may have no plan to ever release it. Releasing it now, though, if it is unpatched is kind of pointless in the long run. Keep it hidden and private, and work with it for as long as you can then release when patched. (Of course, this means a lot of people will probably be caught off-guard by a patch and the kexploit will just be as "limited" as smhax is in what it can do since it runs into much the same problems as smhax in terms of working as a piracy vector (since that seems to be the only thing any one cares about), it just has a further reach that smhax hasn't yet achieved.)
In the latter case, don't expect it for a long, long time.
New