<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 04:09:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-97901 — genetlink: pin family module during policy dump</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-97901</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;genetlink: pin family module during policy dump&lt;/p&gt;
&lt;p&gt;The generic netlink controller&amp;#39;s policy dump keeps pointers to the target
family&amp;#39;s operation and policy tables in its callback state.  A dump may be
split across multiple skbs and remain pending after the initial request.&lt;/p&gt;
&lt;p&gt;Netlink pins the module which owns the dump callback, but in this case
that is the controller&amp;#39;s owner rather than the target family&amp;#39;s owner.  The
target family can consequently be unregistered and its module unloaded
while a policy dump is pending.  Advancing the dump then dereferences
policy memory from the unloaded module.&lt;/p&gt;
&lt;p&gt;Take a reference to the target family&amp;#39;s module when the dump starts.
Drop it from the error and done paths.  This matches the lifetime for which
the dump context retains the family and policy pointers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;genetlink: pin family module during policy dump&lt;/p&gt;
&lt;p&gt;The generic netlink controller&amp;#39;s policy dump keeps pointers to the target
family&amp;#39;s operation and policy tables in its callback state.  A dump may be
split across multiple skbs and remain pending after the initial request.&lt;/p&gt;
&lt;p&gt;Netlink pins the module which owns the dump callback, but in this case
that is the controller&amp;#39;s owner rather than the target family&amp;#39;s owner.  The
target family can consequently be unregistered and its module unloaded
while a policy dump is pending.  Advancing the dump then dereferences
policy memory from the unloaded module.&lt;/p&gt;
&lt;p&gt;Take a reference to the target family&amp;#39;s module when the dump starts.
Drop it from the error and done paths.  This matches the lifetime for which
the dump context retains the family and policy pointers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-97901</guid>
    </item>
  </channel>
</rss>
