<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hardening on vmlinuz</title>
    <link>https://vmlinuz.pl/en/tags/hardening/</link>
    <description>Recent content in Hardening on vmlinuz</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>2025-2026 vmlinuz.pl</copyright>
    <lastBuildDate>Tue, 09 Jun 2026 10:00:00 +0100</lastBuildDate>
    <atom:link href="https://vmlinuz.pl/en/tags/hardening/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kernel Security Checker: which loaded modules grow your attack surface</title>
      <link>https://vmlinuz.pl/en/posts/kernel-security-checker-modules/</link>
      <pubDate>Tue, 09 Jun 2026 10:00:00 +0100</pubDate>
      <guid>https://vmlinuz.pl/en/posts/kernel-security-checker-modules/</guid>
      <description>&lt;p&gt;Every loaded kernel module is a piece of code running with the highest privileges. The more you have, the larger your attack surface. The catch is that a typical system loads modules nobody deliberately enabled: legacy network protocols, exotic filesystems, drivers for hardware you do not even own.&lt;/p&gt;&#xA;&lt;p&gt;So far &lt;a href=&#34;https://vmlinuz.pl/en/kernel-checker/&#34;&gt;Kernel Security Checker&lt;/a&gt; looked at your configuration and kernel version. Now there is a third angle: what is actually loaded right now.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
