markdownlint improvements.

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

Author: garloff

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

@@ -81,15 +81,15 @@ _Exploiting these vulnerabilities requires access to the system and the ability
 to execute code there, thus the categorization as Local Privilege Escalation (LPE),
 not Remote Code Execution (RCE)._
 
-## Update 2026-05-13: Fragnesia 
+## Update 2026-05-13: Fragnesia
 
 Yet another network fragment handling issue which fails to properly prevent
 in-place en/decryption which can be made to hit sensitive page cache contents
 that was put there with splice has been discovered with
-{Fragnesia](https://www.openwall.com/lists/oss-security/2026/05/13/3).
+[Fragnesia](https://www.openwall.com/lists/oss-security/2026/05/13/3).
 It's a simple logic error where the sharing property is forgotten in buffer
 coalescing. It has gotten CVE-2026-46300.
- 
+
 ## Update 2026-05-15: ssh-keysaign-pwn
 
 This LPE is unrelated to the others; under certain circumstances, the kernel
@@ -269,7 +269,7 @@ relevant modules.
 
 ## Outlook
 
-The density with which severe issues are currently found is notable.  While the
+The density with which severe issues are currently found is notable. While the
 research in the referenced issues originated from human beings being suspicious
 that certain things were not handled correctly everywhere, they were assisted
 by AI tools in the search. This pattern is likely to turn up a relevant number
@@ -283,7 +283,7 @@ that gave defenders some headway against attackers. One reason is that
 once a pattern emerges, several teams compete for speed to find related issues
 and decide in favor of disclosing before someone else finds it also. Another
 reason is that there are people that now use AI tools to analyze merged bugfixes
-to the kernel using AI tools -- the fact that they are not flagged as security
+to the kernel using AI tools - the fact that they are not flagged as security
 issues no longer is a good cover. So software distributors need to expect more
 of these occurences where they are struggling to patch software, validate the
 fixes and ship to customers before large-scale attacks happen. Operators will
@@ -299,7 +299,7 @@ is an open question.
 
 The authors would like to thank Taeyang Lee at Xint (who initiated the
 research on copy.fail) and Hyunwoo Kim (@v4bel, who discovered Dirty Frag).
-Update 2026-05-15: They would also like to acknowledge William Bowling (V12) for Fragnesia 
+Update 2026-05-15: They would also like to acknowledge William Bowling (V12) for Fragnesia
 and Jann Horn and Qualys for ssh-keysign-pwn.
 They would also like to thank the upstream Linux kernel maintainers and
 Linux distributors for their reliable work no handling the issues and