<?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://cve.radiocsirt.org</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, 06 Oct 2026 20:01:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47369 — s390/qeth: fix NULL deref in qeth_clear_working_pool_list()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47369</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;s390/qeth: fix NULL deref in qeth_clear_working_pool_list()&lt;/p&gt;
&lt;p&gt;When qeth_set_online() calls qeth_clear_working_pool_list() to roll
back after an error exit from qeth_hardsetup_card(), we are at risk of
accessing card-&amp;gt;qdio.in_q before it was allocated by
qeth_alloc_qdio_queues() via qeth_mpc_initialize().&lt;/p&gt;
&lt;p&gt;qeth_clear_working_pool_list() then dereferences NULL, and by writing to
queue-&amp;gt;bufs[i].pool_entry scribbles all over the CPU&amp;#39;s lowcore.
Resulting in a crash when those lowcore areas are used next (eg. on
the next machine-check interrupt).&lt;/p&gt;
&lt;p&gt;Such a scenario would typically happen when the device is first set
online and its queues aren&amp;#39;t allocated yet. An early IO error or certain
misconfigs (eg. mismatched transport mode, bad portno) then cause us to
error out from qeth_hardsetup_card() with card-&amp;gt;qdio.in_q still being
NULL.&lt;/p&gt;
&lt;p&gt;Fix it by checking the pointer for NULL before accessing it.&lt;/p&gt;
&lt;p&gt;Note that we also have (rare) paths inside qeth_mpc_initialize() where
a configuration change can cause us to free the existing queues,
expecting that subsequent code will allocate them again. If we then
error out before that re-allocation happens, the same bug occurs.&lt;/p&gt;
&lt;p&gt;Root-caused-by: Heiko Carstens &amp;lt;hca@linux.ibm.com&amp;gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;s390/qeth: fix NULL deref in qeth_clear_working_pool_list()&lt;/p&gt;
&lt;p&gt;When qeth_set_online() calls qeth_clear_working_pool_list() to roll
back after an error exit from qeth_hardsetup_card(), we are at risk of
accessing card-&amp;gt;qdio.in_q before it was allocated by
qeth_alloc_qdio_queues() via qeth_mpc_initialize().&lt;/p&gt;
&lt;p&gt;qeth_clear_working_pool_list() then dereferences NULL, and by writing to
queue-&amp;gt;bufs[i].pool_entry scribbles all over the CPU&amp;#39;s lowcore.
Resulting in a crash when those lowcore areas are used next (eg. on
the next machine-check interrupt).&lt;/p&gt;
&lt;p&gt;Such a scenario would typically happen when the device is first set
online and its queues aren&amp;#39;t allocated yet. An early IO error or certain
misconfigs (eg. mismatched transport mode, bad portno) then cause us to
error out from qeth_hardsetup_card() with card-&amp;gt;qdio.in_q still being
NULL.&lt;/p&gt;
&lt;p&gt;Fix it by checking the pointer for NULL before accessing it.&lt;/p&gt;
&lt;p&gt;Note that we also have (rare) paths inside qeth_mpc_initialize() where
a configuration change can cause us to free the existing queues,
expecting that subsequent code will allocate them again. If we then
error out before that re-allocation happens, the same bug occurs.&lt;/p&gt;
&lt;p&gt;Root-caused-by: Heiko Carstens &amp;lt;hca@linux.ibm.com&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47369</guid>
    </item>
  </channel>
</rss>
