<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vulnerability Management on Christoph Kemetmüller</title><link>https://xn--kemetmller-feb.com/tags/vulnerability-management/</link><description>Recent content in Vulnerability Management on Christoph Kemetmüller</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Christoph Kemetmüller</copyright><lastBuildDate>Wed, 14 Oct 2026 00:15:39 +0200</lastBuildDate><atom:link href="https://xn--kemetmller-feb.com/tags/vulnerability-management/index.xml" rel="self" type="application/rss+xml"/><item><title>The Kernel's New Rules for AI Bug Reports</title><link>https://xn--kemetmller-feb.com/blog/the-kernels-new-rules-for-ai-bug-reports/</link><pubDate>Fri, 22 May 2026 14:39:04 +0200</pubDate><guid>https://xn--kemetmller-feb.com/blog/the-kernels-new-rules-for-ai-bug-reports/</guid><description>&lt;p&gt;When Linus Torvalds released Linux 7.1-rc4 on May 17, he flagged a documentation update as the highlight. The substance is a policy: the kernel&amp;rsquo;s security workflow is being restructured to cope with what he called a security list that has become &amp;ldquo;almost entirely unmanageable.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>