<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Linux on investigator&#39;s notes</title>
    <link>https://karmine05.github.io/dirtyfrag-blog/tags/linux/</link>
    <description>Recent content in Linux on investigator&#39;s notes</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 08 May 2026 13:30:00 -0400</lastBuildDate>
    <atom:link href="https://karmine05.github.io/dirtyfrag-blog/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pre-CVE Threat Response: A Dirty Frag Walkthrough with Fleet</title>
      <link>https://karmine05.github.io/dirtyfrag-blog/posts/pre-cve-response-with-fleet/</link>
      <pubDate>Fri, 08 May 2026 13:30:00 -0400</pubDate>
      <guid>https://karmine05.github.io/dirtyfrag-blog/posts/pre-cve-response-with-fleet/</guid>
      <description>How to respond to a public Linux exploit before it has a CVE assigned, using artifact-based queries instead of vulnerability catalogs. A worked example with Fleet, osquery, and a Slack bot wired to MCP.</description>
    </item>
  </channel>
</rss>
