<?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>Wed, 30 Sep 2026 11:44:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49098 — Drivers: hv: vmbus: Fix potential crash on module unload</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49098</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;Drivers: hv: vmbus: Fix potential crash on module unload&lt;/p&gt;
&lt;p&gt;The vmbus driver relies on the panic notifier infrastructure to perform
some operations when a panic event is detected. Since vmbus can be built
as module, it is required that the driver handles both registering and
unregistering such panic notifier callback.&lt;/p&gt;
&lt;p&gt;After commit 74347a99e73a (&amp;#34;x86/Hyper-V: Unload vmbus channel in hv panic callback&amp;#34;)
though, the panic notifier registration is done unconditionally in the module
initialization routine whereas the unregistering procedure is conditionally
guarded and executes only if HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE capability
is set.&lt;/p&gt;
&lt;p&gt;This patch fixes that by unconditionally unregistering the panic notifier
in the module&amp;#39;s exit routine as well.&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;Drivers: hv: vmbus: Fix potential crash on module unload&lt;/p&gt;
&lt;p&gt;The vmbus driver relies on the panic notifier infrastructure to perform
some operations when a panic event is detected. Since vmbus can be built
as module, it is required that the driver handles both registering and
unregistering such panic notifier callback.&lt;/p&gt;
&lt;p&gt;After commit 74347a99e73a (&amp;#34;x86/Hyper-V: Unload vmbus channel in hv panic callback&amp;#34;)
though, the panic notifier registration is done unconditionally in the module
initialization routine whereas the unregistering procedure is conditionally
guarded and executes only if HV_FEATURE_GUEST_CRASH_MSR_AVAILABLE capability
is set.&lt;/p&gt;
&lt;p&gt;This patch fixes that by unconditionally unregistering the panic notifier
in the module&amp;#39;s exit routine as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49098</guid>
    </item>
  </channel>
</rss>
