Release. And fix info on the disclosure process.

Signed-off-by: Kurt Garloff <kurt@garloff.de>

Author: garloff

blog/2026-05-10-kernel-root-exploits.md

@@ -124,7 +124,8 @@ The fixes for Dirty Frag are still in development as of May 8. The first fixes
 have been merged upstream and released in 7.0.5, 6.18.28, 6.12.87, 6.6.138,
 6.1.172, 5.15.206 and 5.10.255 but there is
 [more to come for rxrpc](https://lwn.net/ml/all/2026050859-ahead-anchovy-05e2@gregkh/).
-The responsible disclosure process for Dirty Frag was unfortunately broken,
+The responsible disclosure process for Dirty Frag unfortunately failed due to the
+[patches being spotted](https://www.openwall.com/lists/oss-security/2026/05/07/12),
 so the upstream maintainers and the distributors this time did not have time
 to carefully prepare and test fixes ahead of the publication of the issue.
 So we have to expect that it will take a few days until all Linux distributor
@@ -252,3 +253,4 @@ SCS security contact is [security@scs.community](mailto:security@scs.community),
 - Initial Draft, v0.1, 2026-05-08, 17:15 CEST.
 - kubectl node-shell instructions, v0.2, 2026-05-09, 12:45 CEST.
 - Mention succssful patching of community infra, v0.3, 2026-05-09, 13:30 CEST.
+- Correct facts on the failure of the responsible disclosure. Release as v1.0, 2026-05-09, 20:00 CEST.